Enable interactive input for dotnetup prompts#218
Open
Redth wants to merge 1 commit into
Open
Conversation
Forward opt-in xterm input to active process stdin so dotnetup setup menus can accept navigation and confirmation keys. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: 4ae088bc-2250-4e42-a218-731f5d7d76d3
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.
Why
dotnetupcan display a terminal setup menu during SDK installation, but Sherpa's process modal was output-only. The process remained blocked because users could not send arrow keys or Enter to the running command.What changed
dotnetupSDK installs on Apple pseudo-terminals, including tracked-channel installs.Validation
DotnetUpServiceTestsFixes: #203