Fix install.sh to read user input from /dev/tty#6
Merged
Conversation
When run via curl | bash, stdin is the script itself, so read gets garbage. Reading from /dev/tty ensures the user is prompted correctly. Co-Authored-By: Claude Opus 4.6 (1M context) <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.
Summary
Fix
readin install.sh to use/dev/ttyinstead of stdin, so it works when run viacurl | bash.Problem
When piped through
curl | bash, stdin is the script content itself.read -rpreads from stdin and gets garbage, resulting in broken variable expansion in the install path.Fix
Read from
/dev/ttyexplicitly, which always points to the user's terminal.Test plan
curl -fsSL .../install.sh | bashprompts correctly and installs to the chosen directory🤖 Generated with Claude Code