Re: Problem with vimdiff and file name resolution

On 2014-07-11, Павлов Николай Александрович wrote:

> On July 11, 2014 11:38:15 AM GMT+03:00, Erik Christiansen wrote:
> >On 10.07.14 16:54, Gary Johnson wrote:
> >> On the other hand, a file system such as we're using for backups
> >> seems pretty unusual, and equal inode numbers over network file
> >> systems is also pretty rare. Is this problem worth fixing? Would a
> >> patch even be considered? Or should I just resort to workarounds
> >> for the few times I have to recover part of a file?
> >
> >How many minutes would it take to bang together a shellscript wrapper
> >around vimdiff, to copy one of the files to /tmp/fred, and vimdiff
> >that?

> One can use
>
> vimdiff <(cat file1) <(cat file2)

That's close to the workaround I actually used. I wanted to edit
the current copy with the backup copy as reference, so I did this:

vimdiff <(cat backup) current

Regards,
Gary

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