-
Notifications
You must be signed in to change notification settings - Fork 30.9k
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
Alt + Numpad keybindings insert characters into editor #22364
Comments
+1 |
Not just up and down. left at least will insert a character. |
really irritating |
Minimal repro steps:
Presing the key combination results in the find widget opening, but then the text |
It's been 6 years, any solution? |
I use a workaround for this issue (Windows only solution):
Now ALT + NUMPAD ARROW is not inserting a character anymore. |
I think this is Windows keyboard behavior (Mac, Linux do have similar techniques). So it cannot/should not be "fixed" by VSCode. This is call Alt-code input. This is purposely used to input special characters using it code. For those who reach here by searching the way to input Unicode characters, use Word or Wordpad, type [Alt+Character number] to input the character, then you can copy it to VSCode or other editors that support Unicode. I have a more detailed guide here if you want. |
This is true only if you have the numlock active. If you turn the numlock off, the behavior of VSCode is wrong. |
BTW, I am now on Ubuntu 24.04. So please consider adopting a x-plat solution. |
Guess the problem will never be fixed by editor. |
I can't understand the reason why it should not be fixed in the editor. |
Old schoold people like me, still want the numlock key disabled. This means that "ALT + arrows" (and using the arrows on the numpad of a desktop keyboard) results in inserting an ascii code instead in addition to the keyboard shortcut defined in VSCode.
Steps to Reproduce:
ALT + Up Arrow (on the numpad) lead to inserting the character ◘
ALT + Down Arrow (on the numpad) lead to inserting the character ☻
I expect the behavior is consistent with Visual Studio where ascii characted are never injected on these keyboard combinations.
Thanks
The text was updated successfully, but these errors were encountered: