Re: Re: Problem with vimdiff and file name resolution

2014-07-17 Thread Gary Johnson
On 2014-07-11, Christian Brabandt wrote: > 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 > >pat

Re: Problem with vimdiff and file name resolution

2014-07-12 Thread Jeff Fisher
Hello, It looks like you are using a netapp filer to store the files. The netapp uses filesystem snapshots to make backups of the files, then mounts these snapshots under the root of the mount point. On the netapp side, they are two distinct file systems. However, on the client side, it is a sing

Re: Problem with vimdiff and file name resolution

2014-07-11 Thread Bram Moolenaar
Gary Johnson wrote: > > > On one of the Linux machines on which I run Vim we run a backup > > > program which creates hourly and nightly backups of each user's home > > > directory in ~/.snapshot. The problem is that when I try to view > > > the differences between a file and its backup copy usi

Re: Problem with vimdiff and file name resolution

2014-07-11 Thread Gary Johnson
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

Re: Problem with vimdiff and file name resolution

2014-07-11 Thread Christian Brabandt
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 wo

Re: Problem with vimdiff and file name resolution

2014-07-11 Thread Павлов Николай Александрович
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 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 >> syste

Re: Problem with vimdiff and file name resolution

2014-07-11 Thread Erik Christiansen
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

Re: Problem with vimdiff and file name resolution

2014-07-10 Thread Gary Johnson
On 2014-07-10, Gary Johnson wrote: > On 2014-07-10, Gary Johnson wrote: > > On 2014-07-10, Bram Moolenaar wrote: > > > > Did you check the inode numbers on the files? ls --inode. > > > Vim checks if files are the same, ignoring links, by comparing the inode > > > and devide number. > > > > I was

Re: Problem with vimdiff and file name resolution

2014-07-10 Thread Gary Johnson
On 2014-07-10, Gary Johnson wrote: > On 2014-07-10, Bram Moolenaar wrote: > > Did you check the inode numbers on the files? ls --inode. > > Vim checks if files are the same, ignoring links, by comparing the inode > > and devide number. > > I was going to try that before, but thought it unnecessa

Re: Problem with vimdiff and file name resolution

2014-07-10 Thread Gary Johnson
On 2014-07-10, Bram Moolenaar wrote: > Gary Johnson wrote: > > > On one of the Linux machines on which I run Vim we run a backup > > program which creates hourly and nightly backups of each user's home > > directory in ~/.snapshot. The problem is that when I try to view > > the differences betwee

Re: Problem with vimdiff and file name resolution

2014-07-10 Thread Bram Moolenaar
Gary Johnson wrote: > On one of the Linux machines on which I run Vim we run a backup > program which creates hourly and nightly backups of each user's home > directory in ~/.snapshot. The problem is that when I try to view > the differences between a file and its backup copy using vimdiff, > vi

Re: Problem with vimdiff and file name resolution

2014-07-10 Thread Christian Brabandt
On Do, 10 Jul 2014, Gary Johnson wrote: > I'll work on a way to reproduce it. If you have a chance, take a look at main.c line 2389 That changes the arguments for the files. Best, Christian -- Es verlohnt sich nicht, daß man alle Bücher widerlegt. Exzerpieren isoliert und hebt eine Sache heraus

Re: Problem with vimdiff and file name resolution

2014-07-10 Thread Gary Johnson
On 2014-07-10, Christian Brabandt wrote: > Hi Gary! > > On Mi, 09 Jul 2014, Gary Johnson wrote: > > On one of the Linux machines on which I run Vim we run a backup > > program which creates hourly and nightly backups of each user's home > > directory in ~/.snapshot. The problem is that when I try

Re: Problem with vimdiff and file name resolution

2014-07-10 Thread Christian Brabandt
Hi Gary! On Mi, 09 Jul 2014, Gary Johnson wrote: > On one of the Linux machines on which I run Vim we run a backup > program which creates hourly and nightly backups of each user's home > directory in ~/.snapshot. The problem is that when I try to view > the differences between a file and its bac

Problem with vimdiff and file name resolution

2014-07-09 Thread Gary Johnson
On one of the Linux machines on which I run Vim we run a backup program which creates hourly and nightly backups of each user's home directory in ~/.snapshot. The problem is that when I try to view the differences between a file and its backup copy using vimdiff, vimdiff resolves both file names t