vimrc VS local_vimrc

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

Other approaches are available as well. For instance, autocommands in the .vimrc are possible as well, but every time you move around that directory you'd have to update the autocommand.

Regarding project management, .exrc is enough as long we're working on simple project where everything is in the same directory. On real project I've ended up needing and writing much, much more.

buffer wise, from a local vimrc for instance, with let b:tag_options = { 'no_auto': 0}

snake is one of the possible naming policies. Several are hard-coded: snake, UpperCamelCase, lowerCamelCase, SCREAMING_SNAKE_CASE. Other can be configured (in local vimrc plugins for instance), and then used where we can expect it to make sense: member variables, local variables, static variables, types, getter...

I'm not sure about the new plugin advertised, but 'exrc' is restricted to the current directory. Its settings won't be applied to subdirectories -- unlike to what other localvimrc plugins do