>Aha! Running gvim as root should source all the scripts above _except_
>/home/steve/.vimrc and /home/steve/.gvimrc -- however -u NONE should forbid
>loading any vimrc. Well, let's use what we have:
>
>- What do /home/steve/.vimrc and /home/steve/.gvimrc contain?
/home/steve/.vimrc contains:
set ruler
set showcmd
set incsearch
set ignorecase
set history=500
set expandtab
set tabstop=4
set autoindent
set smartindent
set shiftwidth=4
set showmatch " show matching braces
/home/steve/.gvimrc contains:
set co=120
set lines=45
set guifont=Monospace\ 8
>- Do you have a /root/.vimrc and/or /root/.gvimrc ? If you do, what do _they_
>contain?
Those files do not exist.
This is driving me nuts. I've tried a couple of other things too.
I started gvim with -V and --nofork, captured the output. I compared the log
from the regular start up and from the sudo start up and they logs were
functionally identical.
I compared the :scriptnames from both and they were the same.
As steve, I was able to cat every script listed in the scriptnames list. My
first instinct was that this is a permissions problem. Alas, I haven't been
able to find any unreadable files anywhere.
If you have any other ideas, I'd love to hear them. Thanks for your help so far.
-sc
____________________________________________________________________________________
Never miss an email again!
Yahoo! Toolbar alerts you the instant new Mail arrives.
http://tools.search.yahoo.com/toolbar/features/mail/
