Skip to content

docs: Windows install line that runs from cmd or PowerShell - #17

Merged
NaNIsaac merged 2 commits into
mainfrom
feat/one-line-install
Nov 4, 2026
Merged

NaNIsaac merged 2 commits into
mainfrom
feat/one-line-install

Conversation

@NaNIsaac

@NaNIsaac NaNIsaac commented Nov 4, 2026

Copy link
Copy Markdown
Owner

Summary

Show the Windows install line in a form that runs from cmd as well as PowerShell, and under any execution policy:

powershell -ExecutionPolicy Bypass -c "irm -useb <same URL as before>/install.ps1 | iex"

Changed: README.md, README.ko.md and the install.ps1 header. 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

  • No code change. The installer already supports Windows PowerShell 5.1 (-UseBasicParsing), which is what the new line starts. It was not run here, because it changes the user PATH even with a custom install dir.

powershell -ExecutionPolicy Bypass -c "irm -useb ... | iex" works from cmd and from PowerShell and
under any execution policy. The installer itself is 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.
@NaNIsaac
NaNIsaac merged commit 409229b into main Nov 4, 2026
11 checks passed
@NaNIsaac
NaNIsaac deleted the feat/one-line-install branch November 4, 2026 23:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant