On 20/09/09 03:48, Tim Chase wrote:
>
>> 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
Dissimilarities or not, I agree 100% with the last sentence above your
signature. One of the reasons my vimrc grew (since I came here when Vim
6.1.xxx was current) is that I'm rather sedentary; at one time I ran Vim
under two different Linux OSes, plus Windows (both native and Cygwin),
but all on a single triple-boot machine and with a single vimrc (on the
FAT32 partition with softlinks from $HOME/.vimrc on the other two) --
that was the most I ever had, and one thing it taught me was to pay
attention to portability and include if has() and if exists() wherever
the help mentioned that various versions behave differently, even if all
those I actually had behaved in fact the same way. "Plan ahead", IOW,
for the time when a version with different compiled-in features might
come around.
If I were to "jump between umpteen machines" as you do, I might keep a
vimrc and a few homewritten scripts (keymaps, after-ftplugins, maybe
even my "almost-default" colorscheme, etc.) on a USB key and travel with
that -- and probably invoke Vim with a -u parameter pointing to that. If
the employer^Wcustomer wanted me to work for any length of time on a
machine (or on several) with no USB port and either no Internet access
or a firewall preventing me from accessing the version of my vimrc that
I've uploaded on my home site, he'd have to be very, very, very
$$$convincing$$$ or find someone else to work for him. But then I
understand that other people have different priorities. For instance I'm
retired and a bachelor. A 35-years-old with six kids in school might be
in a much worse bargaining position, even in a two-salary household.
Best regards,
Tony.
--
hundred-and-one symptoms of being an internet addict:
133. You communicate with people on other continents more than you
do with your own neighbors.
--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---
