unix-setup VS Vim

Just go into terminal. I've settled with zsh after forever with bash, but nothing really changed.

It works in all systems, mac, linux, even Windows (with WSL). The same script that I configure it can be used anywhere so I put it on git and just pull that whenever I need to configure a new system for temp/permanent use: https://github.com/Aperocky/unix-setup

Setting up vim (and other shell setups) have been the easiest things ever and this does it for me:

https://github.com/Aperocky/unix-setup

I had to do it several times over the years, even have a shell file that would install all the plugins straight from git. The process take no more than 5 minutes and I'm right at home in the terminal of the new machine.

vim with massive amount of plugin is my go to.

My vim setup looks like atom in terms of interface: https://github.com/Aperocky/unix-setup/blob/master/.vimrc

Very easy to setup, just add the .vimrc file and run the git clone commands after setting up pathogen (package interface). This setup is pretty nice to edit ts/js/py/rb and C family of languages.

This doesn't really work for any of the JVM languages however, those you probably want an IDE.. I tried my best in vim and it just don't work.

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