5 ms·
These vimrc posts are not always very useful. Actually, it should be reminded that each line in vimrc may have bad side-effects. It may increase Vim instance lo
by gbog 15y ago
These vimrc posts are not always very useful. Actually, it should be reminded that each line in vimrc may have bad side-effects. It may increase Vim instance loading time, and increase editing footprint, or slowdown processes like highlighting and scrolling.
Moreover, and probably worse, each specific configuration increases the distance between your daily Vim-fu and the one you'll have to use on another user or another machine. And these occasions have been, in my experience, those when great Vim-fu was the most critical (eg. trying to keep your hand on a dying server on a flooded connection, or showing off your skills on your boss's Mac during plane trip). All this holds for bashrc too. The closest to the default is the best, to some extent.
I take vimrc posts as good occasions to proofread mine and remove all unused stuff. I just commented out a very weird "set notagbsearch" which was probably killing my <ctrl>-].
- hack_edu 15y agoI like your style. Care to share yours?
- gbog 15y agoVim 7 in terminal exclusively: I have the classic things about backspace, black background, statusbar, hlsearch, autocomplete, etc. Then I have a few shortcuts on <Function keys>, because these cannot override other bindings. The most important is <F9> linked to pastetoggle. I also have some specific settings for my current main language (Python). I try to avoid rebinding normal keys because it can kill you when you get used to your tweaks and have to use another instance, but one thing I do is imap <ins> <Nop>, because I hate being suddenly thrown in replace mode. Plugins I have grep.vim linked to <F3> and I'm currently trying NERD_commenter.vim on <F6>
- lynndylanhurley 15y agoWell then you have to extend the argument to plugins as well, and certain plugins (SnipMate, AutoComplPop, Fugitive, etc.) can increase productivity by several orders of magnitude. It's best to store your .vimrc + .vim/ folder on GitHub or a thumb-drive for easy restoration rather than crippling yourself with a limited configuration. Someone else mentioned Homesick (https://github.com/technicalpickles/homesick https://github.com/technicalpickles/homesick) which works really well.
- slmbrhrt 15y agoYeah, I've found that over the years my .vimrc gets shorter and shorter because I rewrite it from scratch with each new environment, taking with me only what I remember through everyday use. I'm down to 30 lines now, counting whitespace.