-
Notifications
You must be signed in to change notification settings - Fork 29.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
KDE: Reading keyboard layout reads the wrong one #23505
Comments
Tested on macOS, the result is as expected. |
@rebornix Does this correct itself in any way if VS Code is restarted? i.e. in Linux we do not detect keyboard layout changes. Can you please start VSCode fresh under this keyboard layout and include perhaps the entire key mapping debug buffer. It appears the C++ module tells us shift+7 creates & -> which looks to me like the English kb layout was detected by the C++ module. Also, if you scroll up, at the top of the file we print the detected keyboard layout. I just wanna double check that we're not simply suffering here from a case of changing the kb layout after VS Code is up and running |
Here are my reproduce steps:
My CentOS is running in Parallel Desktop. So I tried below steps
It still doesn't rule out the possibility that Parallel Desktop may cause this issue. I'll see if @Tyriar can reproduce this issue.
|
@Tyriar mentioned that this is maybe because I don't have |
Thanks for digging into this. @rebornix Looks like X11 is stuck in us
I am no expert on CentOS, but from above it appears X11 is aware of multiple kb layouts, but us is the selected one. Can you please try: |
After running
|
From this last piece of information, it appears that under CentOS, X11 is "disconnected" from the keyboard layout OS functionality. I'm not sure what we should use in this case to detect keyboard layouts |
Related: #24166 |
Let's track in #24166 which contains valuable workarounds and clarifies the problem. |
Ref #23315
OS: CentOS Linux release 7.2.1511 (Core)
Language: German
The builtin keyboard layout detector is correct,
shift+7
generates/
in system terminal, but our keymap sees it as&
.The text was updated successfully, but these errors were encountered: