Error message when opening file in windows

[skeept]

First of all, thank you for your plugins and work in vim. I read the mailing list almost everyday, I find the discussions interesting, but I usually have nothing to contribute :)

When opening a file with gvim in windows (windows 8, 64 bit) I get the following error message:

Error detected while processing function recover#ConfirmSwapDiff: line 34: E484: Can't open file C:\Users\Alatar\AppData\Local\Temp\VIo10B1.tmp 'TERM' is not recognized as an internal or external command, operable program or batch file.

I also have the different menu with the options diff, quit... I choose diff and the script tells me no difference exits and I can delete the file. So the plugin works fine, it just gives me an error message...

Maybe there is a way of avoiding this?

Thanks!

[chrisbra]

Hi skeept!

On Do, 27 Dez 2012, skeept wrote:

First of all, thank you for your plugins and work in vim. I read the mailing list almost everyday, I find the discussions interesting, but I usually have nothing to contribute :)

When opening a file with gvim in windows (windows 8, 64 bit) I get the following error message:

Error detected while processing function recover#ConfirmSwapDiff: line 34: E484: Can't open file C:\Users\Alatar\AppData\Local\Temp\VIo10B1.tmp 'TERM' is not recognized as an internal or external command, operable program or batch file.

I also have the different menu with the options diff, quit... I choose diff and the script tells me no difference exits and I can delete the file. So the plugin works fine, it just gives me an error message...

Maybe there is a way of avoiding this?

Thanks for the feedback. I think I have fixed this bug with the latest commit.

regards,

Christian

Wie man sein Kind nicht nennen sollte: Indy Kator

[skeept]

Thanks for looking into this.

This is what is happening now:

When I open the file a cmd.exe window appears with the following title:

c:\windows\systems32\cmd.exe /c (vim -u NONE -U NONE -es -V ^"C:\path\to\file^" ^>C:\path\to\Temp\VIo1A0F.tmp 2^>^&1)

Nothing happens until I close this window manually. When I close this window manually I get the error messages:

Error detected while processing function recover#ConfirmSwapDiff: line 35: E484: Can't open file C:\path\to\Temp\VIo925C.tmp Vim: Caught close event

(Note that the tmp file from the error message is different from the tmp file in the cmd window, not sure this makes a difference).

At this point (after I manually close the previous window, I see the dialog to choose from one of diff, open Read-Only....) I choose diff, and like before it tells me that there are no differences I asks me if I want to delete the old swap file.

Regards, Jorge

[chrisbra]

Hi skeept!

On Fr, 28 Dez 2012, skeept wrote:

Thanks for looking into this.

This is what is happening now:

When I open the file a cmd.exe window appears with the following title:

c:\windows\systems32\cmd.exe /c (vim -u NONE -U NONE -es -V ^"C:\path\to\file^" ^>C:\path\to\Temp\VIo1A0F.tmp 2^>^&1)

Hm, at first thought, the redirection seems broken. Please set your 'srr' option to something like '>', e.g. :set srr='>'

Also while vim is running, can you make sure, this commandline works correctly:

vim -u NONE -U NONE -es -V ^"C:\path\to\file^" ^>C:\path\to\Temp\VIo1A0F.tmp

(replace by whatever values you see in the cmd line window.)

Also the escaping looks weird, does it work, if you remove the escapes (^) from the command line ?

Thanks.

regards,

Christian

Epsilon hoch x statt e hoch x zu schreiben, hieße Euler nach Athen tragen.

[skeept]

If I modify srr as you suggest this is what happens:

the new cmd window will start in ex mode with these contents: C:\Windows\system32\cmd.exe /c ( vim -u NONE -U NONE -es -V ^"test.tex^" '^>' C:\Users\Alatar\AppD ata\Local\Temp\VIo734C.tmp) "test.tex" "test.tex" [readonly][unix format] 619 lines, 24638 characters Entering Ex mode. Type "visual" to go to Normal mode.

typing args gives: :args [test.tex] ' \Users\Alatar\AppData\Local\Temp\VIo734C.tmp

I type quit in that window twice in a row, that window closes giving the dialog to choose an option. Quitting from that dialog gives

Error detected while processing function recover#ConfirmSwapDiff: line 12: E484: Can't open file C:\Users\Alatar\AppData\Local\Temp\VIo734C.tmp line 35: E484: Can't open file C:\Users\Alatar\AppData\Local\Temp\VIo428E.tmp 6 more lines

If I type vim -u NONE -U NONE -es -V ... without the ^ it gives me the previous cmd window as before that I need to close by typing quit.

Regards, Jorge

[chrisbra]

Hi skeept!

On Fr, 28 Dez 2012, skeept wrote:

If I modify srr as you suggest this is what happens:

the new cmd window will start in ex mode with these contents: C:\Windows\system32\cmd.exe /c ( vim -u NONE -U NONE -es -V ^"test.tex^" '^>' C:\Users\Alatar\AppD ata\Local\Temp\VIo734C.tmp) "test.tex" "test.tex" [readonly][unix format] 619 lines, 24638 characters Entering Ex mode. Type "visual" to go to Normal mode.

typing args gives: :args [test.tex] ' \Users\Alatar\AppData\Local\Temp\VIo734C.tmp

I type quit in that window twice in a row, that window closes giving the dialog to choose an option. Quitting from that dialog gives

Error detected while processing function recover#ConfirmSwapDiff: line 12: E484: Can't open file C:\Users\Alatar\AppData\Local\Temp\VIo734C.tmp line 35: E484: Can't open file C:\Users\Alatar\AppData\Local\Temp\VIo428E.tmp 6 more lines

If I type vim -u NONE -U NONE -es -V ... without the ^ it gives me the previous cmd window as before that I need to close by typing quit.

Ok, seems like, it doesn't work like this on windows. I have taken out that for now. Please test with current head from github.

Thanks!

regards,

Christian

Ein Blinder und ein Tauber wollen sich duellieren. Sagt der Blinde: "Ist der Taube schon da?" Sagt der Taube: "Hat der Blinde schon geschossen?"

[skeept]

I tested and it works fine, It immediately opens the dialog.

Thanks again for fixing this.

Regards, Jorge