vimrc

The key to learning vim for me was to create my own vimrc from the ground up.

Plugins aren't installed until you call:PlugInstall You can also use.nvimrc instead.vimrc, so only nvim instance on server gets plugins.

Check them out and see if there are things you like, but build your own vimrc.

My Vim knowledge applies 100% to any default Vim installation on a modern distro, and my vimrc contains mostly trivial tweaks.

I haven't looked at Atom yet, but can it parse the vimrc file to load the right settings?

If you do that you should be fine without imposing an arbitraty vimrc length.

Stick to a fairly basic standard install and a.vimrc of 50 lines, tops.

I have a small vimrc that's mostly tab-related stuff, so I don't think it's that.

I use block selection so often that I've switched the mappings in my vimrc.

The first thing I would recommend you is to build the vimrc yourself.

> and about elaborate.vimrc's that take you so far away from 'standard' that you're crippled without them.

Looking naively at github files by type is unreliable, since so many people do things like keep their.vimrc and.vim files on github which artificially inflates the number of.vimL repositories.

As for being "cripped" without my vimrc, well, moving tiny text files around is pretty much a solved problem at this point.

My.vimrc now has "inoremap jj <Esc>" in it, and that was the final missing piece to get me into uninterrupted-productivity mode with Vim.

The most useful shortcut I have in my.vimrc is the ability to "sudo save": command W:execute ':silent w!sudo tee % > /dev/null' |:edit!