Re: vimdiff noob question

On Monday, June 9, 2014 11:59:04 AM UTC-5, wolfv wrote:
>
> Thanks for looking into this some more.
> I can open and edit vim files as usual when not in diff mode.

Including the files you're diffing? And they're not empty when you edit them outside of diff mode?

> a.txt and b.txt files are in C:\Users\wolf\Documents\
> What does that mean? - "using the real System32 folder for 32-bit processes"

Windows' "virtual store" means that if you try to create a file in certain protected system folders, you can get some sort of shadow copy instead. I don't remember the details. Maybe this helps: http://www.sevenforums.com/general-discussion/222389-what-virtual-store-folder.html

Windows' "WOW64" redirection means that since Vim is 32-bit, if it tries to access the C:\Windows\System32 directory on a 64-bit system (containing 64-bit apps) it will instead get redirected to C:\windows\SysWOW64.

Both of these scenarios can make Vim edit a file in a different location than you intended.

But it looks like you're editing in your user directory and these should not affect you.


Have you tried disabling all plugins and using a stripped-down .vimrc, containing only the diff setup? The diffexpr should not be deleting all file contents...

--
--
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.