VsVim | Vim Emulator Plugin for Visual Studio | Text Editor library

There is no easy way out for avoiding conflicts between vscode shortcut and vscodevim bindings. I suggest you to use vim keybindings instead of vscode shortcuts wherever possible. Vscodevim can prove to be a good gateway to vim provided you are open to relearning how you use vscode.

Instead of building your own configuration that doesn't collide with vscodevim you could redirect the effort in finding a way to do the same thing in vim. You can search web or use vim help.

Vim help is really comprehensive and easy to read. If you have vim installed you can use :help or :h followed by a specific subject, for example if you need to read about navigation type :h navigation.

Now you have two choices and I will try to use example you provided i.e. saving a file :

1. Use bindings available for saving file in vim.

   Vim provides so many shortcuts just for saving and quitting files, in vim try :help write and :help quit to know more. Many of those shortcuts works in vscodevim too.

   To save file :

   • :w to save a single file

   • :wa to write all buffers (in vscode all modified files).

2. Remove the bindings from vscodevim and use vscode shortcut.

   You can delegate the key combination back to vscode. I suggest you do this only if there is any vscode shortcut that is absolutely necessary for you and it conflicts with vscodevim as doing this may result in some related vim bindings to not work. To know what Ctrl+k does in vim type :h ctrl-k in vim.

   If you want to use Ctrl+K S for saving file do following:

   • Open vscode settings and search for vim handlekeys or directly open vscode's settings.json:

   • add following "vim.handleKeys": {"": false}

I don't know if this a better solution but I was in your situation and tried different ways to solve it. Finally I found it was much easier to use vim keybindings than trying to coerce vscodevim.

Apparently in VSCodeVim, capture groups are recognized with $1, $2, etc.. rather than \1, \2, etc...

So, using this worked:

For now, I found a workaround by using a ~/.vsvimrc file. I just set a has_vsvim variable in .vsvimrc, then source my normal .vimrc file, in which I can check for the has_vsvim flag.

~/.vsvimrc: