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
@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
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
Activity
rebornix commentedon Mar 28, 2017
Tested on macOS, the result is as expected.
alexdima commentedon Mar 29, 2017
@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
rebornix commentedon Mar 29, 2017
Here are my reproduce steps:
ps aux|grep 'code'to make sure no Code instance is active.7,/and two othersshift+7and it generates/shift+7generates&. The complete key mapping is as below.My CentOS is running in Parallel Desktop. So I tried below steps
shift+7generates/, which is perfect.shift+7again. It still generates&.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 commentedon Mar 29, 2017
I think everything is fine on Ubuntu
rebornix commentedon Mar 29, 2017
@Tyriar mentioned that this is maybe because I don't have
libxkbfile-devel.x86_64. Triedsudo yum install libxkbfile-devel.x86_64but still no luck.alexdima commentedon Mar 29, 2017
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:
setxkbmap de,us,cnand in the same terminal launch vscode.rebornix commentedon Mar 29, 2017
After running
setxkbmap de,us,cnin terminal, I run into below issuesctrl+shift+7. But pressingctrl+shift+7works.shift+7in editor and terminal generate&instead of/.y, the system Keyboard Layout Viewer thinks I'm pressing onz(as it's German layout) but the editor still getsy.alexdima commentedon Mar 29, 2017
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
15 remaining items