Bill McCarthy wrote:
Hello Vim Developers,
I was timing the startup process by stepping though what I
think Gvim does (on Win XP Pro with 7.0.42).
gvim -u NONE -N
That starts up without _vimrc or _gvimrc or plugins and sets
nocp.
:so $vim\_vimrc
worked fine.
:so $vim\_gvimrc
also worked fine.
:ru! plugin\**\*.vim
didn't seem to do anything. Repeating the above as
:verb ru! plugin\**\*.vim
reports: not found in 'runtimepath': "plugin\**\*.vim"
Hmm, when I tried again with the unixy
:ru! plugin/**/*.vim
the plugins were finally sourced.
Bug?
IIUC, it's a feature: \* means a literal asterisk. Not a very good
feature since IIUC, asterisks are not allowed in filenames on Windows.
Or can they happen in long file names?
... Don't you have a HOME directory? On XP, I would expect that to
default to %HOMEDRIVE%%HOME£PATH% if you don't define it (something like
C:\Documents and Settings\<username> ) -- and, since XP is a multiuser
OS, it allows each user to have a different set of preferences. $VIM,
OTOH, would normally be something like C:\Program Files\Vim , which is
the same for everyone.
Best regards,
Tony.