You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is rather a question than a bug report, but I have no idea where to start.
I have recently added vscode-neovim to VSCode on my Windows 10 machine and was rather satisfied with the results, which inspired me to try it in VSCode on macOS (Sonoma on Apple silicon).
The important fact is that in both systems I am using Czech localized keyboard layout (on both systems the one called "Czech"). While on Windows the localized keyboard works fine, on macOS as soon as I switch to the CZ layout I cannot emit ESC control code (to quit insert mode, etc.) by using the <C-ú> combo.
Looking at the keyboard mapping in VSCode while using CZ layout shows that while in Windows the <C-[> is correctly remapped the <C-ú>, (character ú in CZ layout is written by the same key as [ in US layout), on macOS, the mapping simply vanishes and reappears when switching back to US layout.
Both machines run the same VSCode version 1.87.2
Few screenshot to illustrate what I mean by "mapping simply vanishes".
Windows using US layout, with correct mapping:
Windows using CZ layout, with correct mapping:
macOS using US layout and having correct mapping:
macOS using CZ layout and missing the <C-ú> mapping:
What I found interesting is that the displayed mapping in VSCode changes on the fly when switching the keyboard layouts. So it looks like VSCode knows how to process the "input source" change in both systems. Since it also puts back the correct one in the US version, it looks like the definitions are correct, but for some reason the localized one on macOS does not make it to the actual interpretation (of the mappings) and does not work as well.
This discussion was converted from issue #1868 on April 03, 2024 20:45.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
This is rather a question than a bug report, but I have no idea where to start.
I have recently added
vscode-neovim
to VSCode on my Windows 10 machine and was rather satisfied with the results, which inspired me to try it in VSCode on macOS (Sonoma on Apple silicon).The important fact is that in both systems I am using Czech localized keyboard layout (on both systems the one called "Czech"). While on Windows the localized keyboard works fine, on macOS as soon as I switch to the
CZ
layout I cannot emitESC
control code (to quit insert mode, etc.) by using the<C-ú>
combo.Looking at the keyboard mapping in VSCode while using
CZ
layout shows that while in Windows the<C-[>
is correctly remapped the<C-ú>
, (characterú
inCZ
layout is written by the same key as[
inUS
layout), on macOS, the mapping simply vanishes and reappears when switching back toUS
layout.Both machines run the same VSCode version 1.87.2
Few screenshot to illustrate what I mean by "mapping simply vanishes".
Windows using
US
layout, with correct mapping:Windows using
CZ
layout, with correct mapping:macOS using
US
layout and having correct mapping:macOS using
CZ
layout and missing the<C-ú>
mapping:What I found interesting is that the displayed mapping in VSCode changes on the fly when switching the keyboard layouts. So it looks like VSCode knows how to process the "input source" change in both systems. Since it also puts back the correct one in the
US
version, it looks like the definitions are correct, but for some reason the localized one on macOS does not make it to the actual interpretation (of the mappings) and does not work as well.Beta Was this translation helpful? Give feedback.
All reactions