Skip to content
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

Swapped keys (CAPS LOCK <-> ESCAPE) are not applied #2419

Closed
rok-povsic opened this issue Mar 5, 2018 · 1 comment
Closed

Swapped keys (CAPS LOCK <-> ESCAPE) are not applied #2419

rok-povsic opened this issue Mar 5, 2018 · 1 comment

Comments

@rok-povsic
Copy link

Is this a BUG REPORT or FEATURE REQUEST? (choose one):
Bug report.

What happened:
I have CAPS LOCK and ESC swapped as escaping is more common for me than switching typing case. The swap works everywhere - in all programs, terminal etc., including VS Code menues - except when actually typing the text, using VS Code Vim, i.e. when trying to get out of the normal mode.

For example, what happens now is the following - when in insert mode:

  • pressing the CAPS LOCK key - no effect,
  • pressing the ESCAPE key - goes to normal mode AND current typing case is switched.

What did you expect to happen:

I'd expect ESC and CAPS LOCK to be swapped same as everywhere else in the system.

How to reproduce it (as minimally and precisely as possible):

Using Gnome Tweak Tool, enable the swap:
image

I've also tried using another swap keys approach, by modifying /usr/share/X11/xkb/symbols/pc (as per this post) with same result.

Environment:

  • Extension (VsCodeVim) version: 0.11.0
  • VSCode version: 1.20.1
  • OS version: Ubuntu 16.04, Gnome 3.18.2

Thank you a lot. I greatly enjoy using VS Code & the Vim plugin.

@rok-povsic rok-povsic changed the title Swapped keys are utilized Swapped keys (CAPS LOCK <-> ESCAPE) are utilized Mar 5, 2018
@rok-povsic rok-povsic changed the title Swapped keys (CAPS LOCK <-> ESCAPE) are utilized Swapped keys (CAPS LOCK <-> ESCAPE) are not applied Mar 5, 2018
@Chillee
Copy link
Member

Chillee commented Mar 7, 2018

This is a bug on VSCode's end. View a workaround here: #1479 (comment)

@Chillee Chillee closed this as completed Mar 7, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants