Just curious, and maybe this question is out of place. I'll admit that I don't have enough background on how ports have historically worked. But to me, storing 3rd party (ports) application config files in system's /etc directory just sounds and looks wrong.
At best I would think a global vimrc file should go into /usr/local/etc. Not the system /etc. I'm just saying. --patrick --- Tobias Ulmer <[EMAIL PROTECTED]> wrote: > On Mon, Jul 10, 2006 at 02:40:37PM -0600, Chris Kuethe wrote: > > On 7/10/06, Tobias Ulmer <[EMAIL PROTECTED]> wrote: > > >Nobody speaks up, so i will ;) The whole point of this is that I don't > > >like to have the (always global) vimrc file in > > >/usr/local/share/vim/vimrc. All ports are expected to have their config > > >files in etc, right? > > >If you have custom plugins that you want to make available for everyone > > >-> put it into /usr/local/share/vim/vim70/autoload? It sure will break > > >pkg_delete. What if you want to change something in a supplied plugin? > > >pkg_add will break on the next update > > > > > >Btw, even if that does not count that much. Debian has the same setup. > > > > > >Now if that doesn't convince you, i don't know what does ;) > > > > I suppose I'd be OK with adding support for a global configuration in > > /etc/vim, so long as we leave an example in /usr/local/share and let > > the local admin copy it in. I tried your patch which does install a > > global vimrc, and suddenly my .vimrc didn't work the way I expected. > > > > CK > > > > -- > > GDB has a 'break' feature; why doesn't it have 'fix' too? > > > > > > Yes they are merged together and .vimrc can overwrite/reset anything. > > Anyway, I'm just looking for the posibility to place files in > /etc/vim to keep my config files in as few places as possible :) > No need to install the samples by default. > > Tobias > > __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
