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

Previous Next

Full log

View this message in rfc822 format

From: John Wiegley <jwiegley <at> gmail.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 23276 <at> debbugs.gnu.org, michael.albinus <at> gmx.de, andlind <at> gmail.com
Subject: bug#23276: 25.0.92; Crash in auto-revert when file no longer present
Date: Sat, 16 Apr 2016 19:53:02 -0700

>>>>> Eli Zaretskii <eliz <at> gnu.org> writes:

>> 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?

I'm not sure, but I never clobber files that way...

> Don't we have a variant of auto-revert that never shrinks the buffer?

I think if it's significantly reduced, it does warn. But I'm not sure what
that's based on.

The current behavior, whatever it is, does not lose contents that get
accidentally deleted from disk.  I'm not sure what happens if you cat
/dev/null onto your code.

-- 
John Wiegley                  GPG fingerprint = 4710 CF98 AF9B 327B B80F
http://newartisans.com                          60E1 46C4 BD1A 7AC1 4BA2

Previous Next

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