vscode-kotlin VS Vim

I find the Vim extension for VS Code has macro support that is good enough for most of my use cases (if you’re a fan of Vim key bindings - obviously).

https://github.com/VSCodeVim/Vim/blob/master/ROADMAP.md#repe...

that's why I just use https://github.com/VSCodeVim/Vim if I have to use VSCode

This post is all over the place. What are you asking? What problem exactly did you have with the https://github.com/vscode-neovim/vscode-neovim (ensure that you did not install https://github.com/VSCodeVim/Vim , which people often confuse with the other).

What you would learn from using a neovim addon for VS Code covers most of the first point and some of the second - VSCode Vim lets you run neovim in a headless mode that relays keypresses to it, and emulates several popular addons. It also comes without quite as much hassle as comes from the second step of learning to configure vim/neovim yourself. Most VSCode extensions work pretty well out of the box, maybe requiring you to add the path to a compiler/interpreter that is not on your PATH.

Either I go with K552 or save for RK84 if not CB-GK-16 and both of these are pretty good choice that's certain, or I go with 617 Fizz and use VIM keybinding which Isn't an issue for me cause I've been using NeoVim for more than 1 year, you can grab my dotfiles if you want. Most people won't go with 60% cause they are used to arrow, home, end ... keys so am I with vs code but today I found out about vscodevim extension which enables vim keybinding , these keybindings pretty easy to use more than arrow, home, end .. keys if yo're a vim user like Shift + $ = end, Shift + 0 = home, in visual mode V to select text etc ...

There is also VSCodeVim extension: https://github.com/VSCodeVim/Vim which afaik does not use any external programms.

We're all biased here because you're asking in a neovim community. You should ask in a helix community but I think they'll also agree that you should learn vim first. Neovim and vim are the same in terms of modal editing. You may try vscodevim so that it doesn't change too much of your workflow and you can focus on the basic movement. And also you don't need to think about the neovim plugin ecosystem for now until you're comfortable with vanilla vim movement. For jetbrains products there are vim binding emulators too so it's more universal. I use vim emulator in intellij.

Are you familiar with vim q macros? It's a similar thing but you don't need to use maps/remaps to use them: q to start recording and q (in normal mode, so q sometimes) to stop recording. Then you can rerun the macro with @ (or @@ is rerun the last macro). (Even fun things like @ work to rerun the macro a number of times.)

VSCodeVim seems to support q-macros just fine. The lone silly missing bit is that VSCodeVim makes it slightly tougher to save/reuse q-macros than proper Vim [1]. In Vim those letters are the exact same "registers" as copy/paste so that you can record a macro to register 'a' with `qa…q` and then if you want to save that macro for later you can just paste it into a document somewhere `"a` (paste register a) and pull the macro back in with the right motion and yank to the register you want (`ya`). VSCodeVim unfortunately uses separate registers for now and it is a bit more work to save/restore q-macros.

[1] https://github.com/VSCodeVim/Vim/issues/1658

Checkmate: https://github.com/VSCodeVim/Vim