Workaround to fix arrow keys on non-conhost Windows terminals #1
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
…t and non-conhost Windows terminals
|
Thank you for the PR! Just to check, will you also be submitting the same to PDCurses project? |
|
@igrr Yes I'm planning to report this to the upstream PDCurses. I'm sure they'll come up with a more elegant solution than my hack though. |
|
How would I manually update mine to have this fix? |
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.
The traditional conhost.exe terminal on Windows seems to treat arrow keys differently from other terminals, which is not accounted for in PDCurses. This adds some virtual key translations to make arrow keys work in non-conhost terminals like VSCode or Windows Terminal Preview.