emacs-noob VS Vim

Emacs works reasonably fine. Here's a branch that intends to provide the more familiar key bindings.

PS: I do have an emacs-noob/slime-company that might come handy. This shouldn't depend on anything specific to the OS. (Check the different branches to see which suits the OP/reader's needs!)

(Shameless plug) I'm maintaining a (still quite experimental because I don't personally use it) emacs-noob for people new to emacs but not wanting any long term relation with emacs, or want to focus on learning common lisp first and emacs second. You might find slime-company or slime-company-modern branches useful if this fits your use case.

I attempted emacs-noob/emacs-modern for some of my teammates for developing with common-lisp. It's still very much a new and untested thing though.

But if emacs becomes too-difficult-too-soon in most part due to key-bindings (definitely worth learning for life!), I recently had a try at digikar99/emacs-noob/slime-company-modern for some of my friends, which packs "familiar" key-bindings, but does require a separate installation of a compiler.

I suspect I'm not going to find enough time to maintain a full-fledged VSCode key-bound. I've put up something primitive at digikar99/slime-company-modern and digikar99/emacs-modern.

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

They have discussions enabled on the GitHub repository; eventually r/vscode might be of help.

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.

The extension does have visualedit. You can check the list of supported features here: https://github.com/VSCodeVim/Vim/blob/HEAD/ROADMAP.md

I though VSCode's vim emulation had issues with code folding

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 ...