Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Keyboard mappings with `setxkbmap` on Linux not working
See original GitHub issue- VSCode Version: 1.11.0
- OS Version: Ubuntu 16.04
I have my Caps Lock key bound to Escape using setxkbmap on Linux. This worked fine till 1.10, but broke with 1.11. At first I thought it was an issue with the VSCodeVim extension, but the issue persists with all the other Vim extensions on the marketplace as well. Pressing the escape button still works as expected.
The binding is still respected everywhere else in the operating system, it’s only Visual Studio Code that ignores it for some reason.
Steps to Reproduce:
- Run
setxkbmap -option caps:escape(binds caps to escape for the duration of the session) - Hitting caps lock when in insert mode (with a Vim extension like VSCodeVim installed) no longer puts you normal mode.
- Hitting escape still works as expected and puts you in normal mode.
Issue Analytics
- State:
- Created 6 years ago
- Reactions:249
- Comments:89 (8 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
This is something that might be broken by us dispatching based on scan codes. I am sorry about it, I need some time to investigate how these options should be handled. i.e. should Chromium handle these mappings or should we do it at the application layer.
Workaround to switch VS Code to dispatch based on key code again. Add the following setting:
"keyboard.dispatch": "keyCode"and restart VS Code@kylebakerio Maybe don’t use Microsoft software on linux.