On 2/24/07, Nathan Coulter <[EMAIL PROTECTED]> wrote:
bug report
==========
version:
VIM - Vi IMproved 7.0 (2006 May 7, compiled May 7 2006 16:23:43)
MS-Windows 32 bit GUI version with OLE support
problem:
Writing to a file on a windows share where the underlying filesystem
supports hard links, modifying a file using gvim (w command) causes the
file to
acquire a new inode. Contrast with the behavior of notepad.exe (file -
save), which
respects the hard link, keeping the inode intact.
Try ':set backupcopy=yes' in your vimrc.
Does this solve the problem ?
The default mode ('backupcopy=auto') is not guaranteed
to preserve the hardlinks. This is nota bug.
But ':set backupcopy=yes' shall preserve hardlinks. If
':set backupcopy=yes' breaks links, this would be a bug.
Yakov
