vimrc VS badwolf

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

Gruvbox its a retro groove Color scheme heavily inspired by badwolf, jellybeans and solarized. With this I want to give the community a customization theme a little different from what they are used to such as neon and those quirky themes that do not go with the retro theme of the PSP

I used Steve Losh's BadWolf theme with that wallpaper for quite a while https://github.com/sjl/badwolf

Badwolf: https://github.com/sjl/badwolf

badwolf is a custom color scheme plugin. When I launch Vim for the first time on a new machine, I won't have the plugins installed yet, using badwolf immediately will cause it to fail on that first Vim run. evening is a built-in Vim color scheme. By putting silent! colorscheme evening followed by silent! colorscheme badwolf, if badwolf isn't available, it will, in effect, falls back to evening. silent! will also omit the error message (otherwise you'll see an error message when Vim couldn't find badwolf)