[EMAIL PROTECTED] (Miquel van Smoorenburg) wrote: >In article <[EMAIL PROTECTED]>, Danny ter Haar <[EMAIL PROTECTED]> wrote: >>Hint for the maintainer: please set a default of NO backups ! > >Has already been done in the version in slink IIRC
That would be great (haven't checked yet). Note that other people's concerns for vim to do the "safe" thing (i.e. leave the backups until you know how vim works) is bogus, as I've been using vim for at least 5 years (hmmm, version 1.27) and "knew" that vim doesn't leave backups. Otherwise, if backups are preferred, put them somewhere all together like /tmp so that the system isn't littered with these ~ files everywhere. Now to remove the "set tw=78" which causes gratuitious line wraps, very painful when editing e.g. a shell script. Rely on the autocommands to turn this feature on for emails etc, that works fine! Also, put "set directory=~/tmp,/var/tmp,/tmp,.". This causes the "swap file" (where the backup stuff is kept if something happens in the middle of an edit session) to be put in one of those directories, the first if possible etc. That prevents those pesky ".swp" files appearing in the current directory, which screw up your terminal when you do "grep bla *" due to control characters in the swap file being printed. In fact, at one time in Vim development, the current directory was the default, until people protested for the reasons I listed above. Now debian's vim maintainer restored the old problems :-( The first thing I do on a new debian installation is edit /etc/vimrc :-( The second thing is 'rm /etc/vimrc~' ... Paul Slootman -- home: [EMAIL PROTECTED] | work: [EMAIL PROTECTED] http://www.wurtel.demon.nl | Murphy Software, Enschede, the Netherlands "In my opinion MS is a lot better at making money than it is at making good operating systems." (Linus Torvalds, August 1997)
