vimrc VS Vim

there are several vimrc files: https://github.com/amix/vimrc

Vim with https://github.com/amix/vimrc

If you want my five cents, then I would say that using something like https://github.com/amix/vimrc without fully understanding the consequences, is a bad idea. And instead you should focus on the basics of vim, vimtutor followed by :h user-manual.

text editors for writing files. Recommended: install plugins ultimate vim to make vim more powerful and colorful.

Archcraft's vim uses this vimrc which adds a lot of plugins including some for improving appearance, so it's more suited for a terminal emulator than a tty.

I'm basically using this as a base with some tweaks :)

Or if you want something very minimal, just for easier editing experience when connected to server, try just a simple preconfigured vimrc file, where you can comment and uncomment stuff that you might need. I use amix as base for my own vimrc file.

git clone https://github.com/amix/vimrc.git ~/.vim_runtime

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