imho this is exactly the behaviour that is specified by vim itself:
[quote=":help viminfo-file-name"]
The default name of the viminfo file is "$HOME\_viminfo" for MS-DOS and Win32.
When $HOME is not set, "$VIM\_viminfo" is used. When $VIM is also not
set, "c:\_viminfo" is used.
[/quote]
therefore $VIM is only used if $HOME is _not_ set. I think this is not a bug of gvim portable, it is vim's behaviour. If you want to use an other location for your "viminfo", please read ":help E526" and set it in your "vimrc"
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
My two cents: Gvim not only reads _viminfo from $HOME, it also writes a new file if none is present. I think this is not acceptable for a portable application, and should have precedence over the vim specification.
Otherwise, great work!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=1522748
Originator: NO
imho this is exactly the behaviour that is specified by vim itself:
[quote=":help viminfo-file-name"]
The default name of the viminfo file is "$HOME\_viminfo" for MS-DOS and Win32.
When $HOME is not set, "$VIM\_viminfo" is used. When $VIM is also not
set, "c:\_viminfo" is used.
[/quote]
therefore $VIM is only used if $HOME is _not_ set. I think this is not a bug of gvim portable, it is vim's behaviour. If you want to use an other location for your "viminfo", please read ":help E526" and set it in your "vimrc"
My two cents: Gvim not only reads _viminfo from $HOME, it also writes a new file if none is present. I think this is not acceptable for a portable application, and should have precedence over the vim specification.
Otherwise, great work!