(v2) keyboard docs #1169
Open
(v2) keyboard docs #1169
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
Not really. We could ignore the messages instead, i.e. have a different internal flow than Unix platforms. This happens early in the program when we're initializing the terminal. On Windows, we need to tell the terminal handler that we're using the Windows API vs Virtual Escape Codes. |
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 revision expands the keyboard enhancements docs a little to help users find their way around the feature.
One question, @aymanbagabas: is it possible to disable keyboard enhancements on Windows? If not we should adjust the docs here accordingly.