On 16 September 2010 10:03, Dennis Preiser <[email protected]> wrote:
> Bjorn Winckler <[email protected]> wrote:
>> On Sep 15, 2010, at 22:37, Dennis Preiser <[email protected]> wrote:
>>
>>> Brian McKee <[email protected]> wrote:
>>>> Anybody else noticed an issue where their history doesn't seem to be
>>>> available since switching to 7.3?
>>>
>>> Yes. I've noticed that ':e <arrow up>' dosn't recall the files from the
>>> last vim session.
>>
>> Do you both have "quickstart" enabled in the advanced prefs by any chance?
>
> Yes, I have. I thought that effects only subsequent new windows, not the
> initial one.

The problem has to do with when the .viminfo file is read/stored (this
file contains the history).  I think there are (at least) two issues:

1. Say you open MacVim (with quickstart) and edit some files, then
quit and restart.  When you quit there are two vim instances that will
close and write to the .viminfo: the instance you were editing in and
a "hidden" cached instance.  If the cached instance closes last it
will overwrite whatever the first instance wrote to .viminfo.  This
would cause the history to be "lost" when you restart MacVim.

2. You open a new vim instance.  This causes another to be cached in
the background and I think it will pick up on the .viminfo contents
right away.  When you (several edits later) open a new vim instance it
will use the old .viminfo contents that has already been read.  This
would make it seem like the history has been "lost" as well.

Not sure what to do about this.  The .viminfo file simply does not
work that well when you have several instances of vim open at once.
Maybe it would be possible to somehow synchronize the .viminfo with
each open vim instance every now and then, but how would this
heuristic work?  Would there be any new problems because of this?  I
don't know.

Björn

-- 
You received this message from the "vim_mac" 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

Reply via email to