-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Make sure that key bindings work in all IMEs #6439
Comments
This is strange! |
Resolved! @DHowett I use US keyboard layout. { "command": "openNewTabDropdown", "keys": "ctrl+shift+d" }, // will work
{ "command": "openNewTabDropdown", "keys": "ctrl+shift+space" }, // will work under English US but this still not work { "command": { "action": "newTab", "index": 2 }, "keys": "ctrl+shift+3" }, // not work
{ "command": { "action": "newTab", "index": 3 }, "keys": "ctrl+shift+4" }, // not work Before, I used the English status of Chinese input |
I will reopen this issue, because we want to make sure that key bindings work in all IMEs :) |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
I think that part should work now with the introduction of #10876, which was released in Windows Terminal 1.11. |
(also cross-linking: #15598. ctrl+shift+f for find doesn't work with the Microsoft Pinyin IME) |
We discussed this a little while back, and we've come to the conclusion as a team that it's going to be practically impossible for us to avoid conflicts with all keys bound in all possible software that someone might be using with the Terminal. We will try our best to stick to ctrl+shift modifiers for keys we bind in our default settings, to avoid conflicts with CLI apps. And we'll always let users change bindings for keys on their own. But there's not much else we can do here to try and avoid the gambit of other things that might also bind keys. |
Environment
Steps to reproduce
ctrl+,
open settings.json, find keybindings tutorial in microsoft docsmodify some keybindings like that:
Expected behavior
keybindings work properly
Actual behavior
some keybindings not work
settings.json
GitHub not support upload .json file, modify the extension to .txt
settings.txt
The text was updated successfully, but these errors were encountered: