LazyVim bindings for VSCode

[brotherkaif]

Hello! Not sure if anyone has any interest in this, but I thought I'd share anyway.

Over the past few weeks I've been mapping the LazyVim keybindings to VSCode (that's right, setting up VSCode to behave like LazyVim).

Why am I doing this? LazyVim is my daily driver, but sometimes, I'm forced to use VSCode for liveshare pairing sessions. But, I'm so used to the LazyVim keybindings that I find myself fumbling around VSCode whenever I have to use it.

This settings.json file for VSCode is my attempt to map the same LazyVim bindings to the equivalent VSCode functionality. It's certainly not going to be exactly like LazyVim, but at least the same functionality appears when you use the same keybindings (e.g. <leader>gg will bring up the source control tool in VSCode instead of LazyGit in LazyVim).

If you're interested, here's a gist with the config.

A couple of things to note:

• You need to have the VSCode Vim plugin installed for this to work
• I've laid out the config to be identical to the LazyVim Keymap documentation page to make it easier to read
• There is a lot of mappings that are commented out, either because there isn't a suitable VSCode equivalent, or I just haven't found one yet

Like I said, not sure if anyone has any interest in this, but if anyone has any suggestions for some of the missing ones I'd be more than happy to update the gist.

Thanks!

[spector700]

I am trying to do the same thing, except with the vscode Neovim extension.

Is there a reason that you chose the regular vim one?

[spector700]

Yeah I remapped my surround to the same and I works fine in nvim but vscode just doesn't like it most of the time.

[cStralpt]

maybe you dont configure the extension properly, there's a feature that tell you, weather your vs code get connected or not into lazyvim, you can look at the status bar:

if that does not appear than you're not actually connected to lazyvim, you need to check your VS Code Neovim setup.

[spector700]

Yeah, I already stole a lot of your config, but it connects fine.
Do you have a keybindings.json that is not in your repo?

[cStralpt]

i think you need to add gsa key to your keybindings in order to make it work, because i used to do the same thing to fix problems like this on my config.

[cgjosephlee]

I have this in my config and mini.surround works nice in VSCode, hope it helps.
https://github.com/cgjosephlee/dotfiles/blob/master/.config/nvim/lua/plugins/vscode.lua