VCSDiff fails on Windows

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Install plugin on C:\Program Files\Vim\vimfiles\(doc|plugin|syntax)
2. Restart Vim (so plugin is loaded)
3. Do a :VCSDiff

What is the expected output? What do you see instead?
I saw this working on Linux, but it seems to fail on Windows. Instead of
showing the diff screen, I get a

VCSCommand: Vim(edit):E303: Unable to open swap file for "SVN diff
Src\Pages\ImageView.cpp (2)", recovery impossible.

What version of the product are you using? On what operating system?
Vim 7.1, running on Windows XP.

Please provide any additional information below.

Original issue reported on code.google.com by julio.bi...@tilefile.com on 20 Mar 2008 at 2:59

[GoogleCodeExporter]

Is this occur on the third diff you for a file?  Is the '(2)' part of the file 
name?

Original comment by bob.hies...@gmail.com on 21 Mar 2008 at 10:40

[GoogleCodeExporter]

No, it's the first diff. (2) is not part of the file name. I'm guessing VIM is 
adding
it because there is another buffer with the same name and Windows is refusing to
create such file (just blind guessing here, I don't know that much about VIM 
internals.)

Original comment by julio.bi...@tilefile.com on 24 Mar 2008 at 10:28

[GoogleCodeExporter]

I'm unable to duplicate this with Vim 7.1.242 (distributed with Cream) against
vcscommand beta 22.

The vcscommand appends (#) to the end of the command result buffers it creates 
if a
buffer with the same name already exists.   This is why I believe you have 
opened
:VCSDiff twice before.

I'm not sure why the swap file cannot be created.  Immediately after a new 
result
buffer is created, it is set to noswapfile.  Do you have any swap-file-specific 
settings?

Thank you,

bob

Original comment by bob.hies...@gmail.com on 25 Mar 2008 at 3:46

• Added labels: Priority-Low
• Removed labels: Priority-Medium

[GoogleCodeExporter]

AFAIK, I'm not using any swap settings (just using the default ones.) My VIM is 
the
official one, without any other extensions.

If you are interested, I posted my settings on my site:
http://notes.juliobiason.net/doku.php?id=tips:vim

I'm also using Beta 22.

Original comment by julio.bi...@tilefile.com on 25 Mar 2008 at 10:24

[GoogleCodeExporter]

I'm unable to duplicate using your settings and vim 7.1.  Please execute the 
following:

:verbose set directory?

Does the diff buffer appear after the error?

Thank you,

bob

Original comment by bob.hies...@gmail.com on 27 Mar 2008 at 1:44

• Changed state: Accepted

[GoogleCodeExporter]

the :verbose command gave me this:

directory=.,c;\tmp,c:\temp

There is another thing I noticed now (maybe it's the verbose thing)

After a :SVNDiff I got this:

"SVN diff Src\Page.cpp (1)" [New DIRECTORY]
VCSCommand:  Vim(edit):E303: Unable to open swap file for "SVN diff Src\Page.cpp
(1)", recovery impossible

I think it is weird that "[New DIRECTORY]" as the directory is there...

Original comment by julio.bi...@tilefile.com on 27 Mar 2008 at 11:11

[GoogleCodeExporter]

I just found something:

As you may have noticed by the filenames, I don't run Gvim in the same 
directory of
the sources (I keep it on the base directory and open files as "Src\Pages.cpp" 
and
"Group\App.mmp".)

I did a ":cd Src" and called :VCSDiff and then it worked fine.

Original comment by julio.bi...@tilefile.com on 27 Mar 2008 at 11:14

[GoogleCodeExporter]

Scratch that last comment. Suddenly, it is working, but I changed directory to 
just
".". I'll play with that setting for a while to see if that fixes the problem.

Original comment by julio.bi...@tilefile.com on 27 Mar 2008 at 11:16

[GoogleCodeExporter]

The plugin should be happy running in a directory other than that of the current
file, as it was explicitly written for that situation.  Do you have any 
autocommands
that alter your current directory?

Original comment by bob.hies...@gmail.com on 2 May 2008 at 1:36

[GoogleCodeExporter]

I've replicated the defect.  I'm working on a different method of naming the 
buffer
which should avoid the swap file issues.

Original comment by bob.hies...@gmail.com on 20 May 2008 at 3:16

[GoogleCodeExporter]

Please try beta 24:  
http://vcscommand.googlecode.com/files/vcscommand-beta24.zip

It may fix this issue for you.

Original comment by bob.hies...@gmail.com on 20 May 2008 at 6:46

• Changed state: Fixed

[GoogleCodeExporter]

I assume this fixed it for you as it did for me unless I hear otherwise.

Original comment by bob.hies...@gmail.com on 3 Jun 2008 at 4:41

• Changed state: Verified

[GoogleCodeExporter]

It's hard to me to test it now 'cause I'm (thankfully) not using Windows 
anymore. :)

Original comment by julio.bi...@tilefile.com on 3 Jun 2008 at 11:13