> Whenever you feel the need to change this or that detail of your Vim's > default functionality, you'll add a few lines to your vimrc, usually > below what I showed above, and after a couple of years it will have > grown beyond recognition while becoming more and more adequate to your > own style of Vimming.
Tony and I are on pretty opposite ends of this spectrum -- his .vimrc is quite a work of art. Mine is merely a handful of settings that fit on half a screen: set nocp vb ai lbr wrap set ts=2 sw=2 set backspace=indent,eol,start set cpoptions-=x set history=50 set report=0 set suffixes+=.pyc suffixes+=.pyo syntax on colorscheme timchase to ignore python precompiled-output files. I try to keep it fairly close to stock settings as possible because I jump between umpteen machines and don't like to have to keep my .vimrc in sync. Tim O'Reilly puts forth similar reasoning on why he switched from emacs to vim[1]. I like to be able to jump on a machine, fire up vi(m) and have it behave about the same no matter where I go. But then that's one of the beautiful things about vim -- it more than sufficiently meets both Tony's needs and mine despite our dissimilarities. -tim [1] http://oreilly.com/pub/a/oreilly/ask_tim/1999/unix_editor.html --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_use" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
