-
Notifications
You must be signed in to change notification settings - Fork 8.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix #8458: Handle all Ctrl-key combinations #8870
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
God why is input such a disaster 🙃
Thanks for looking into this and fixing it
It might take me until next weekend to fix the failing unit tests by the way. |
Turns out there was a reason why |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wonderful. Thanks.
Hello @miniksa! Because this pull request has the p.s. you can customize the way I help with merging this pull request, such as holding this pull request until a specific person approves. Simply @mention me (
|
🎉 Handy links: |
Pressing Ctrl+\ produces
^\
using the US keyboard layout, thanks to Ctrl-key mappings inside the keyboard layout, whereas some layouts, like the UK extended layout, don't contain those. This causes the character value to be zero and previously caused no VT sequence to be generated under these situations. This PR employsMapVirtualKeyW
to infer the missing characters.As a side effect this PR effectively causes all major keys on the keyboard to produce Ctrl+combinations now.
PR Checklist
Validation Steps Performed
Compared all major keys in combination with Ctrl with the app store version of Terminal using
showkey
in WSL. All keys that previously worked still appear to continue to work.