Re: Problem with vimdiff and file name resolution

Am 2014-07-11 01:54, schrieb Gary Johnson:
> 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?

FWIW: In my opinion, vimdiff should just work[TM], so I would like to
have your fix included. Because if one ever stumbles over your issue,
it's not easy to understand why it happens (if one even notices, that
the bug really happened rather than thinking, "Oh those files must be
the
same, if vimdiff doesn't show me a differenc...")

Best,
Christian

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