GNU bug report logs - #23276
25.0.92; Crash in auto-revert when file no longer present

Previous Next

Full log

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

From: Eli Zaretskii <eliz <at> gnu.org>
To: Óscar Fuentes <ofv <at> wanadoo.es>
Cc: 23276 <at> debbugs.gnu.org
Subject: Re: bug#23276: 25.0.92;
 Crash in auto-revert when file no longer present
Date: Sun, 17 Apr 2016 18:16:28 +0300

> From: Óscar Fuentes <ofv <at> wanadoo.es>
> Date: Sun, 17 Apr 2016 15:20:22 +0200
> 
> Eli Zaretskii <eliz <at> gnu.org> writes:
> 
> >> > And I still am not convinced that deleting a file under auto-revert
> >> > shouldn't erase its buffer. Otherwise, it sounds like just
> >> > half-auto-revert to me. Would we keep the buffer non-empty if the
> >> > file existed but was empty?
> >> 
> >> I would not want it to erase the buffer. Countless have been the times that
> >> I've been working on a project, and an unbridled rm took away code from the
> >> disk which I was very grateful to find was still in a buffer.
> >
> > How is it different from clobbering a file by making it empty?
> 
> $ echo hello > foo.txt
> 
> $ emacs -Q foo.txt &
> 
> M-x auto-revert-mode
> 
> $ echo -n > foo.txt
> 
> M-x undo

How is this relevant to the issue at hand?  Undo is not part of the
picture.

> Clobbering a file doesn't imply that you lose its previous contents.

I never said otherwise.

Previous Next

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