Date: Sun, 16 Nov 2014 11:48:21 -0800 From: Alfred Perlstein <alfred@freebsd.org> To: David Chisnall <theraven@FreeBSD.org>, Baptiste Daroussin <bapt@FreeBSD.org> Cc: Mathieu Arnold <mat@FreeBSD.org>, Olli Hauer <ohauer@FreeBSD.org>, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org, ports-committers@freebsd.org Subject: Re: svn commit: r372622 - in head/editors/vim: . files Message-ID: <5468FF85.8020108@freebsd.org> In-Reply-To: <91D8CCEA-BA20-4185-98FF-145A0F9810D6@FreeBSD.org> References: <201411160232.sAG2WJ4Z084790@svn.freebsd.org> <54687C89.20206@gmx.de> <F61D76AA4CF82F5E4FC8BFAF@atuin.in.mat.cc> <20141116113345.GG45145@ivaldir.etoilebsd.net> <20141116113525.GH45145@ivaldir.etoilebsd.net> <91D8CCEA-BA20-4185-98FF-145A0F9810D6@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 11/16/14, 11:37 AM, David Chisnall wrote: > On 16 Nov 2014, at 11:35, Baptiste Daroussin <bapt@FreeBSD.org> wrote: > >> That said isn't using the default upstream provided vimrc a better option than a >> custom one? >> /usr/local/share/vim/vim74/vimrc_example.vim as vimrc >> and probably /usr/local/share/vim/vim74/gvimrc_example.vim as gvimrc? > I think that would be better. My .vimrc, as a result of following the instructions on the vim web site many years ago, > starts with: > > source $VIMRUNTIME/vimrc_example.vim > > Anyone following the vim upstream instructions will expect to be able to customise the settings by creating a .vimrc that starts like this and then overrides the things that they want to be different. > > Thanks to everyone who's working on this: I recently had one of our students complain that vim on FreeBSD 'defaults to just plain vi' unlike the Linux distributions he was working on. I hadn't noticed the difference, as my .vimrc is one of the first things I copy across to a new system, but on closer investigation he was right and the fix (for him) was trivial: that one-line .vimrc. It would be great if people didn't have to bother with that: if you've gone to the trouble of installing vim (and typing vim instead of vi to launch it), it's probably because you want vim, not vi. > > David > This was my experience exactly, but it was with 3 of our devs! Thanks for validating my experience! I'm going to upload the patch now. -Alfred
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5468FF85.8020108>