On Sun, Sep 02, 2007 at 12:58:46AM +0200, Tony Mechelynck wrote: > > Charles E. Campbell, Jr. wrote: > > sc wrote: > > > >> charles-- > >> > >> again i find myself struggling with netrw > >> > >> i used to love it for directory navigation and finding > >> things, but have come to hate the way it mangles my session > >> settings, specifically formatoptions > > > > v112b shouldn't be changing your format options. > > > >> i went the extra mile to get v112b off your web site, > >> de-install the v110 that was giving me fits, and install > >> v112b in my ~/.vim so it wouldn't get whacked > >> > >> that was several weeks ago > >> > >> what's happening now is that every time i build and install a > >> new patch level, v110 gets put back in place on my > >> /usr/local/share/vim/vim71, and vim searches that first when > >> coming up, effectively making my v112b invisible to vim
> > Your runtimepath is odd -- my runtimepath has /home/cec/.vim as its > > first entry, as it should. So I think you should figure out why your > > runtimepath is wrong; perhaps you have VIMRUNTIME set in your .profile? > > Normally the netrw in your ~/.vim should be loaded first and thereby > > prevent the loading of the system netrw (ie. prevent the loading of > > v110), so if you get your runtimepath issue worked out netrw v112b > > should come up even though the /usr/local/share/vim/vim71 still has v110. > > > >> do i need to write a script to whack the netrws on > >> /usr/local/share and run it at the tail end of my install > >> script, or do you have a better suggestion? > > Fix your runtimepath! Its probably the easiest. > > > > Regards, > > Chip Campbell > > On Linux, the default value is > > ~/.vim,$VIM/vimfiles,$VIMRUNTIME,$VIM/vimfiles/after,~/.vim/after > > or its equivalent after expanding ~ $VIM and $VIMRUNTIME. Any 'runtimepath' > directory other than $VIMRUNTIME need only be created when you have something > to put into it; but in order to install a vimball you need file- and > directory-creation privileges to directories early in 'runtimepath' and their > immediate parent. Normally you ought to have all permissions over your $HOME > directory and anything below it, so that's no problem. > > You (sc) need a _very_ good reason to change 'runtimepath'; and $VIMRUNTIME > should be in the middle, not at one end. waaaa! i'm NOT! i swear!! there's something truly weird that was causing vim to find netrw on /usr/local/share, in spite of my runtimepath=~/.vim,/usr/local/share/vim/vimfiles,/usr/local/share/vim/vim71,/usr/local/share/vim/vimfiles/after,~/.vim/after -- sc --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
