Automatically listen for terminal input when standard input is not a TTY #53
Conversation
This file contains 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
meowgorithm
changed the title
|
Dropping this branch and PR as there's a simpler, better way to do this, particularly on Windows. |
lorenzo-milicia
pushed a commit
to lorenzo-milicia/bubbles
that referenced
this pull request
Mar 5, 2023
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.
This PR automatically captures input as normal if stdin is not a TTY, so long as the user hasn't already specified a custom input. Prior to this update, if data was piped in the Bubble Tea runtime would not capture keystrokes, mouse input and so on by default as input was coming in through a pipe and thus not a TTY.
An example is included in the examples directory called
pipe, which demonstrates this new functionality.Note that prior to this update it was possible to achieve the above via custom input functionality introduced in #39.
Related: #24.