[EMAIL PROTECTED] wrote:
[...]
Now, I would assume that these mappings would be applied either on app
startup or by issuing the '\lps' sequence in normal mode. Neither seems
to be the case. One question I have is: I think that there is a $HOME
variable used by vim, but it may not have a value under windows, and
therefore the paths to these necessary files aren't resolved. Is this a
possibility? Is there a way to check this?
Thanks,
Matt
[...]
On startup, Vim checks the environment and sets some variables if they
aren't defined. Here are the main ones:
$HOME : On Unix it's normally defined. If undefined on Windows, Vim (or
the OS) often sets it to some default such as $HOMEDRIVE$HOMEPATH or
$USERPROFILE. If it sets it to a wrong value, set it yourself using
either C:\AUTOEXEC.BAT or "Control Panel -> System -> Advanced ->
Environment variables" depending on which version of Windows you are
using. A "last resort" fallback for $HOME on single-user systems is the
value of $VIM (see below).
$VIM and $VIMRUNTIME : Vim sets them in a rather complicated manner
which is explained under ":help $VIM" and ":help $VIMRUNTIME". Typical
values are:
$VIM (on Windows): the following are different but synonymous
C:\Program Files\vim
C:PROGRA~1\vim
$VIM (on Unix): the following are not synonymous but IIUC all are typical
/usr/local/share/vim
/usr/share/vim
/opt/kde3/share/vim
$VIMRUNTIME (for version 7.0 "release")
$VIM/vim70
To see how your version of Vim has set those variables, type
:echo "HOME (" . $HOME . ")"
:echo "VIM (" . $VIM . ")"
:echo "VIMRUNTIME (" . $VIMRUNTIME . ")"
Best regards,
Tony.
