Repository navigation
docs: Windows install line that runs from cmd or PowerShell - #61
Merged
Merged
Conversation
powershell -ExecutionPolicy Bypass -c "irm -useb ... | iex" works from cmd and from PowerShell and under any execution policy. The READMEs, the site, the install.ps1 header and the Windows hint in install.sh now show it; the install steps are unchanged.
irm | iex runs the script in the caller's scope, so $ErrorActionPreference = 'Stop' stayed in the interactive session after the install. It is now set inside a script block; only the PATH changes remain.
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
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.
Summary
Show the Windows install line in a form that runs from cmd as well as PowerShell, and under any execution policy:
Changed: README.md, README.ko.md, rust/README.md, the site pages (en/ko), the
install.ps1header and the Windows hint ininstall.sh. Labels say "cmd or PowerShell". The installer logic is unchanged; it already needs nothing preinstalled (it downloads the release binary and checks its SHA-256).Tests
install.ps1from main was run under Windows PowerShell 5.1 withCDG_INSTALL_DIRset to a temp folder, through this exact line and through-File: it installs andcdg --versionworks.shellcheck install.shpasses.