edenzik / macvim

Automatically exported from code.google.com/p/macvim
0 stars 0 forks source link

Swap file information not displayed when using :e or :sp to open a file #94

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
When I open a file from within a Macvim window (e.g. using :e filename or
:sp filename) that already has a vim swap file, the swap file information
usually isn't displayed.  Opening a new file in a new window (e.g. via File
-> Open, or launching a gvim from the command line) seems to always display
the information.

Sometimes I see nothing except the dialog with the open read-only/delete
swap file/edit anyway/etc. buttons, sometimes I see just the red
"ATTENTION" first line of the message at the bottom of the Macvim window,
and sometimes I see the whole swap file info message.  Often, switching to
another window, then switching back lets me see the swap file info.

"Picture 2.png" is what I'd like to see every time, even when using vim
commands such as :e to open a file; "Picture 1.png" is what I usually see
when using :e or :sp.

Original issue reported on code.google.com by namre...@gmail.com on 5 Jun 2008 at 2:51

Attachments:

GoogleCodeExporter commented 9 years ago
Is there a somewhat reliable way of reproducing this bug?  I haven't managed to 
reproduce it once over here, so 
maybe the sequence in which you do things matter.  Can you give me step-by-step 
instructions that reproduces 
this bug for you?

Thanks,
Björn

Original comment by bjorn.winckler@gmail.com on 8 Jun 2008 at 1:59

GoogleCodeExporter commented 9 years ago
Sorry, I do see this problem now...I will see what I can do about it.  Thanks 
for the report!

Original comment by bjorn.winckler@gmail.com on 8 Jun 2008 at 2:10

GoogleCodeExporter commented 9 years ago
I have pushed a patch to the git repo that fixes this.  It will be included in 
the next snapshot.

Original comment by bjorn.winckler@gmail.com on 9 Jun 2008 at 4:48

GoogleCodeExporter commented 9 years ago
Snapshot 31 contains this fix...but it has been reported to have other issues 
so you may want to stay with 
snapshot 28 if it gives you troubles.

Original comment by bjorn.winckler@gmail.com on 18 Jun 2008 at 8:15