Hi Linda,
It looks like you have most of this figured out. I just thought I'd
try to answer some remaining questions.
On 2011-07-14, Linda W wrote:
> Why is it ignoring my .vimrc for a _vimrc
> on an NTFS win7 system? Oh...nevermind...
> I just deleted the _vimrc, and now it picks up .vimrc...
> (Lame!)
See
:help _vimrc
and the first note:
Note: For Unix, OS/2 and Amiga, when ".vimrc" does not exist,
"_vimrc" is also tried, in case an MS-DOS compatible file
system is used. For MS-DOS and Win32 ".vimrc" is checked
after "_vimrc", in case long file names are used.
> :echo $HOME
> i:\
> ----
> Interesting, I have HOME, in my cygwin BASH,
> but not in a raw cmd (one not spawned/run from BASH).
> There, I only have:
> HOMEDRIVE=i:
> HOMEPATH=\
> HOMESHARE=\\BLISS\linda w
>
> Note, that "i:" is 'map'd to \\Bliss\linda w
>
> So it sorta all ties together...but HOME is 'synthetic' on windows.
>
> Cygwin has it closest to 'right', since if I didn't have drive 'i' mapped
> to \\Bliss\linda w, I'm not sure where Vim would get HOME...
Unfortunately there is no help topic on this. However ":helpgrep
HOMEDRIVE" finds these notes in version6.txt:
- When $HOMEDRIVE and $HOMEPATH are defined, use them to define
$HOME. (Craig Barkhouse)
Patch 6.1.146
Problem: MS-Windows: When $HOME is constructed from
$HOMEDRIVE and $HOMEPATH, it is not used for storing
the _viminfo file. (Normal Diamond)
Solution: Set $HOME with the value obtained from $HOMEDRIVE
and $HOMEPATH.
Files: src/misc1.c
Regards,
Gary
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
