Fix why the README avoids curl in the PowerShell install snippet - #50
Open
mattpodwysocki wants to merge 1 commit into
Open
mattpodwysocki wants to merge 1 commit into
mattpodwysocki wants to merge 1 commit into
Conversation
The prior wording said curl "is not guaranteed to be present" on Windows, which hasn't been true since Windows 10 1803 (April 2018) — curl.exe has shipped in System32 ever since, real curl, not a shim. The actual problem is narrower and worth naming precisely: Windows PowerShell 5.1 (the legacy edition that ships with Windows) aliases `curl` to Invoke-WebRequest, whose flags are nothing like real curl's, so typing the commands above there runs the wrong tool silently — even though curl.exe exists right next to it. PowerShell 7 (pwsh) dropped that alias; `curl` there calls the real binary. sha256sum's absence is the one claim that was already accurate, so it keeps its own sentence. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Small, standalone correction — unrelated to the Navigation API work in
flight on other branches.
The README's "Download the archive yourself" section said
curl"is notguaranteed to be present" on Windows, justifying
Invoke-WebRequest/Get-FileHashinstead. That's not accurate for any remotely currentWindows:
curl.exe— real curl, not a shim — has shipped inSystem32since Windows 10 version 1803 (April 2018).
The actual reason to avoid it is narrower and worth naming precisely:
Windows PowerShell 5.1 (the legacy edition that ships with Windows,
powershell.exe) aliasescurltoInvoke-WebRequest, whose flags arenothing like real curl's — so the commands in that section would silently
run the wrong tool there, even though
curl.exeexists right next to it.PowerShell 7 (
pwsh) dropped that alias;curlthere calls the realbinary.
sha256sum's absence outside WSL/Git Bash was already accurate andkeeps its own sentence.
Verified both claims (Windows 10 1803 shipping curl.exe; 5.1 aliasing curl,
7 not) before writing this, rather than assuming.
Not done
Nothing else in this section needed touching.
🤖 Generated with Claude Code