Nathan Coulter 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.
> >
> > What is the 'backupcopy' option set to? It should be "auto", then Vim
> > should be able to recognize hard links on NTFS filesystems.
> >
>
> 'backupcopy' is set to "auto". The hard link is not on an NTFS
> filesystem, but on a network drive shared from a NAS device, Network
> Appliance OnTap 7.0.3p4, configured as a unix filesystem. I access
> this NAS filesystem location from linux and windows computers. From a
> windows computer, a "w" command in Gvim cause assignment of a new
> inode, whereas "file -save" in notepad.exe retains the file inode,
> keeping the hard link intact.
Ah, well, Vim can't know there is a hard link then. You better set
'backupcopy' to "yes". Or avoid hard links, there will probably more
trouble with them.
--
hundred-and-one symptoms of being an internet addict:
208. Your goals for the future are obtaining an T1 connection and
a 130 gig hard drive.
/// Bram Moolenaar -- [EMAIL PROTECTED] -- http://www.Moolenaar.net \\\
/// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\ download, build and distribute -- http://www.A-A-P.org ///
\\\ help me help AIDS victims -- http://ICCF-Holland.org ///
