Neo keyboard layout: Some Keys stopped working
See original GitHub issue- VSCode Version: Code 1.11.0 (9122ec4b1068bd391e41974f46a4b54c1b9c90f9, 2017-04-05T21:13:24.700Z)
- OS Version: Linux x64 4.4.0-72-generic
Steps to Reproduce:
- Install and activate Neo keyboard layout
- Open any source file in VS code
- Put cursor somewhere in the file
- Press
M4
key and hold. Presss
key (see image) - Instead of the cursor moving left, nothing happens
In the previous version of VSCode (1.10.2 8076a19fdcab7e1fc1707952d652f0bb6c6db331) this worked just fine .
Issue Analytics
- State:
- Created 6 years ago
- Reactions:20
- Comments:33 (4 by maintainers)
Top Results From Across the Web
Arrow keys not working with NEO keyboard layout : VIM-987
This is a follow-up on IDEA-135540: The arrow keys on the NEO keyboard layout stop working when the IdeaVim plugin is enabled. This...
Read more >[SOLVED] Some Keys not working correctly with NEO2 ...
Hi, im using Windows with NEO2 Keyboard Layout. Now i noticed that is Segger Embedded Studio some Keys are not working properly.
Read more >Mod4 keys don't work for "German (Neo 2)" keyboard layout
My first keyboard layout is German. The second is "German (Neo 2)". The problem is that the Mod4 don't work for Neo. The...
Read more >Neo/AdNW/KOY Keyboard Layout - Mod4 broken - Ask Ubuntu
Problem is: If i want to use Mod4, aka Layer 4 (on german-qwertz-keys "<" and "AltGr"), this is not possible. I checked with...
Read more >Neo Keyboard Layout is stuck at level 3 / Newbie Corner ...
I had a problem regarding the keyboard layout being stuck in the 3rd layer ... Whenever I started typing, the keys from the...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I need some time to understand this keyboard layout. I will ping you in the coming days if you’d be kind enough to help me out. It is unlike anything I’ve seen.
Workaround to switch VS Code to dispatch based on key code again. Add the following setting:
"keyboard.dispatch": "keyCode"
and restart VS CodeI’m new to VS Code and I use the KOY layout (with some adaptions) on Linux (
setxkbmap de koy
). Same problem as with Neo2: I can type a hyphen by pressingCapsLock+L
in the editor. But shortcuts containing CapsLock don’t work (like zooming out withCtrl+-
=Ctrl-CapsLock-L
).The keybindings issues page recommends running <kbd>F1</kbd>
> Developer: Inspect key mappings
if nothing else helps.With the standard German layout (
setxkbmap de
), I get this for the <kbd>L</kbd> key:With KOY (
setxkbmap de koy
), I get:Apparently, VS Code doesn’t get the higher levels of the layout right!
Some additional technical information about this keyboard layout family (neo, adnw, koy, bone):
In the German default layout, <kbd>AltGr</kbd> is mapped to
ISO_Level3_Shift
(in Linux). In Neo2 (and alike), <kbd>AltGr</kbd> is mapped toISO_Level5_Shift
and <kbd>CapsLock</kbd> is mapped toISO_Level3_Shift
.So I think, we should see in the output of
> Developer: Inspect key mappings
either(because CapsLock replaces AltGr in Neo2 in terms of being the new
ISO_Level3_Shift
key)or
(because you get a “6” when you press the physical <kbd>AltGr</kbd> key plus the <kbd>L</kbd> key as you can see in OP’s screenshot).
I hope, this helps you VS Code developers better understanding our problem.
I’m aware that I (and others) are mixing some issues concerning Neo here. But they might be related.
Tested on Ubuntu 18.04 with this version of VS Code/Codium: