Tuesday, June 10, 2014

Re: vimdiff noob question

On Tuesday, June 10, 2014 2:04:19 PM UTC-6, Ben Fritz wrote:
> On Tuesday, June 10, 2014 10:44:29 AM UTC-5, wolfv wrote:
> > Both gvim diff and vim diff causes a.txt and b.txt to become empty:
> > C:\Users\wolf\My Documents>vim -d a.txt b.txt
> > C:\Users\wolf\My Documents>gvim -d a.txt b.txt
> > Same with --noplugin option:
> > C:\Users\wolf\My Documents>vim --noplugin -d a.txt b.txt
> > C:\Users\wolf\My Documents>gvim --noplugin -d a.txt b.txt
> > There was no error message about a swap file existing already.
> >
> > where vim is running from:
> > C:\>where vim
> > C:\Program Files (x86)\Vim\vim74\vim.exe
> >
> > VIM - Vi IMproved splash page says "version 7.4.256"
> >
> > version from in within C:\>"Program Files (x86)\Vim\vim74\vim.exe"
> > :version
> > VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Apr 11 2014 15:27:34)
> > MS-Windows 32-bit console version
> > Included patches: 1-256
> > Compiled by digitectNO@SPAMdancingpaper.com:http://SteveHallArchitecture.com
> > Huge version without GUI. Features included (+) or not (-):
>
> Everything looks like it should be working :-(
>
> I've never seen behavior like this; it works fine for me.
>
> Maybe we can narrow down where the file gets deleted on your system.
>
> Is it when you create a diff? Try this:
>
> gvim -O a.txt b.txt
> :windo diffthis
>
> Or maybe, it is because you launch a second Vim to edit the same file(s):
>
> gvim -o a.txt b.txt
> vim -o a.txt b.txt

Ben,
The commands you posted produced something interesting, read on.

I manually set a.txt and b.txt to contain unique lines of text.
Then from Command Prompt:
gvim -O a.txt b.txt
opens gvim showing both files as empty.
Looking at Windows Explorer preview pane confirms that both files are indeed empty.
Then from inside gvim:
:windo diffthis
A window flashes (opens and closes very fast), but it's too fast for me to see what it is.

I manually reset a.txt and b.txt to contain unique lines of text.
Then from Command Prompt:
gvim -o a.txt b.txt
opens gvim showing both files as empty.
But looking at Windows Explorer preview pane, I can see that a.txt is empty and b.txt still contains the original text.
Then from Command Prompt:
vim -o a.txt b.txt
an error message pops up:
C:\PROGRA~2\Vim\vim74\vim.exe is not a valid Win32 application.
[OK]
I click the "OK" button and the Command Prompt line says:
Access is denied.

I think we are on to something. What does it mean?
Screen shot of Command Prompt is attached.

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

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

No comments:

Post a Comment