GNU bug report logs - #16718
bug in vi on linux

Previous Next

Package: coreutils;

Reported by: Cheng Ong <Cheng.Ong <at> brisbane.qld.gov.au>

Date: Tue, 11 Feb 2014 02:32:01 UTC

Severity: normal

Tags: notabug

Done: Assaf Gordon <assafgordon <at> gmail.com>

Bug is archived. No further changes may be made.

Full log


Message #11 received at 16718 <at> debbugs.gnu.org (full text, mbox):

From: Pádraig Brady <P <at> draigBrady.com>
To: Cheng Ong <Cheng.Ong <at> brisbane.qld.gov.au>
Cc: 16718 <at> debbugs.gnu.org
Subject: Re: bug#16718: bug in vi on linux
Date: Tue, 11 Feb 2014 09:28:11 +0000
tag 16718 notabug
close 16718
stop

On 02/11/2014 02:02 AM, Cheng Ong wrote:
> Hi there,
> 
> Just encountered a bug in VI.
> Editing file 'x' using vi, when done, content of file 'x' was saved as well in file 'y'.
> File 'y' has no relation to file 'x' and is sitting in a different directory.
> Only relation was file 'x' was created through a cp command from file 'y'.
> Now changes made either on file 'y' or 'x' appear in both files.

I'm guessing you linked the file names.
http://vim.wikia.com/wiki/Editing_a_hard_link_to_a_file

If you can repeat this without specifying any options to cp,
then it might be a bug in cp, but it's quite unlikely,
so I'm closing this for now.

These commands should verify:

env cp x y
[ $(stat -c %i x y | uniq | wc -l) = 1 ] && echo possible cp bug
cp --version

thanks,
Pádraig.




This bug report was last modified 6 years and 284 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.