> -------Original Message------- > From: Bram Moolenaar <[EMAIL PROTECTED]> > Subject: Re: gvim, Windows NAS share of a unix file system, hard links > Sent: 2007-02-25 09:42 > > > 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. -- Nathan Coulter
