Bug in GetLatestVimScripts -- or in Vim?
- To: vim-dev mailing list
Bcc: Dr. Chip (who doesn't want his addy to be harvested).
Bug symptom: GetLatestVimScripts clobbers the 'viminfo' option. The bug
seems to be due to ":set nocp" clobbering the 'viminfo' option even if
'compatible' is already FALSE.
Details: One of my projects relies on a project-specific viminfo, which is
set in a project-specific vimrc. Surprise! ":verbose set vi?" now answers
Last set from D:\HOME\VIMFILES\PLUGIN\GetLatestVimScripts.vim
Searching the source of GetLatestVimScripts.vim (as downloaded from
vim-online) doesn't find a "let" or "set" statement referring to the viminfo
option. I suspect the "set nocp" at the beginning might be the culprit, but
'compatible' should already be off by the time the plugin is sourced, so I
would expect "set nocp" to do nothing. I'm puzzled. Is it a bug in Vim or in
I'm using gvim 6.3.017 on W98; the binary and its full ":version" listing
are published on my website.
-- Experiment: Replacing
in the plugin, then reloading gvim, makes the problem disappear; and now the
answer to "verbose set vi?" is
Last set from D:\chroniq\_vimrc
which is the value I want.
- Dnia sobota, 28 sierpnia 2004 23:44, Antoine J. Mechelynck napisał:
> To: vim-dev mailing listNoticed similar behaviour for 'showcmd'
> Cc: Bram
> Bcc: Dr. Chip (who doesn't want his addy to be harvested).
> Bug symptom: GetLatestVimScripts clobbers the 'viminfo' option. The bug
> seems to be due to ":set nocp" clobbering the 'viminfo' option even if
> 'compatible' is already FALSE.
> Details: One of my projects relies on a project-specific viminfo, which
> is set in a project-specific vimrc. Surprise! ":verbose set vi?" now
LaTeX + Vim = http://vim-latex.sourceforge.net/
Vim-list(s) Users Map: (last change 10 Mar)
CLEWN - http://clewn.sf.net