Vim VS vscode-emacs-mcx

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.

Hi Mickey, ah no -- you've done WAY more than me in this area! I had been meaning to try your combobulate package.

FWIW: after 20 years of Emacs I personally switched to VSCode a couple of years ago because I felt that in Emacs I was missing out on the LSP experience that VSCode provided in Rust, Typescript, Scala, etc. (I was using Eglot). In any case, there's a very nice Emacs emulation mode in VSCode

https://github.com/whitphx/vscode-emacs-mcx

which includes some paredit functionality courtesy of

https://robert.kra.hn/past-projects/paredit-js.html

and I'm working on porting my favorite paredit function, paredit-kill. Unfortunately that's the one where the paredit author left this comment in the code:

  ;;; Please do not try to understand this code unless you have a VERY

It has been requested in the issue, but not been implemented yet; https://github.com/whitphx/vscode-emacs-mcx/issues/772

Yes. You can configure key assignments through keybindings.json. See https://code.visualstudio.com/docs/getstarted/keybindings#\_advanced-customization Combining multi commands are also possible with multi-command extension. These are examples. https://github.com/whitphx/vscode-emacs-mcx/issues/392 https://github.com/whitphx/vscode-emacs-mcx/issues/965