On Sun, Sep 02, 2007 at 01:32:52AM +0200, Tony Mechelynck wrote:
>
> sc wrote:
> > 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
> >
>
> Yes, that's the default value.
>
> Is the more recent version installed in the plugin/ and autoload/ subdirs of
> one of the above? Not under ~/.vim for a different user (which would have a
> different home dir)? Nor in an after-directory? And you _do_ have read/write
> permission on the files and their directories, don't you?
/home/scott/.vim> find . -name "*netrw*" -print
./doc/pi_netrw.txt
./netrw.vba
./syntax/netrw.vim
./autoload/netrw.vim
./autoload/netrwSettings.vim
./autoload/netrwFileHandlers.vim
./plugin/netrwPlugin.vim
which is indeed v112b, as witness the fact that after running
my:
/home/scott/.build/vim> cat wobn
#!/bin/bash
##
## whack old buggy netrw -- must run as root
##
for f in $(find /usr/local/share/vim/vim71 -name "*netrw*" -print)
do
rm -i $f
done
then v112b is what comes up when i try to :Explore
i am the only user on this box:
/home> ls -Al
total 24
drwx------ 2 root root 16384 Apr 11 14:29 lost+found
drwxr-xr-x 89 scott users 4096 Sep 1 18:46 scott
/home>
now what else did you ask? read/write permissions on the
files and their directories?
files first:
/home/scott/.vim> for f in $(find . -name "*netrw*" -print)
> do
> ls -l $f
> done
-rw-r--r-- 1 scott users 103511 Aug 22 15:58 ./doc/pi_netrw.txt
-rw-r--r-- 1 scott users 365991 Aug 22 15:28 ./netrw.vba
-rw-r--r-- 1 scott users 3152 Aug 22 15:58 ./syntax/netrw.vim
-rw-r--r-- 1 scott users 231897 Aug 22 15:58 ./autoload/netrw.vim
-rw-r--r-- 1 scott users 8069 Aug 22 15:58 ./autoload/netrwSettings.vim
-rw-r--r-- 1 scott users 10226 Aug 22 15:58 ./autoload/netrwFileHandlers.vim
-rw-r--r-- 1 scott users 8875 Aug 22 15:58 ./plugin/netrwPlugin.vim
owned by me and writable by me
now for the directories:
/home/scott/.vim> ls -ld * | grep '^d'
drwxr-xr-x 2 scott users 4096 Sep 1 13:07 autoload
drwxr-xr-x 2 scott users 4096 Aug 22 15:58 doc
drwxr-xr-x 2 scott users 4096 Sep 1 13:04 plugin
drwxr-xr-x 2 scott users 4096 Sep 1 13:05 syntax
> Oh, and, you aren't overriding $VIM and/or $VIMRUNTIME are you? (I suppose
> not, but trying to cover all bases). You ought to see
>
> :echo $VIM
> /usr/local/share/vim
> :echo $VIMRUNTIME
> /usr/local/share/vim/vim71
indeed -- :echo $VIM yeilds:
/usr/local/share/vim
and :echo $VIMRUNTIME yeilds:
/usr/local/share/vim/vim71
this is a true mystery, but one i hope no-one loses any sleep
over -- i've put 'wobn' in my install script, which i run as
root, so i've got a painless work-around -- i may even get to
trust it enough to take the '-i' off the 'rm' -- not soon,
but eventually -- maybe
--
sc
--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---
