GNU bug report logs - #56423
29.0.50; Hi-lock in dired broken by toggling wdired-mode

Previous Next

Full log

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

From: Eli Zaretskii <eliz <at> gnu.org>
To: Michael Heerdegen <michael_heerdegen <at> web.de>
Cc: 56423 <at> debbugs.gnu.org
Subject: Re: bug#56423: 29.0.50; Hi-lock in dired broken by toggling
 wdired-mode
Date: Fri, 08 Jul 2022 15:59:53 +0300

> From: Michael Heerdegen <michael_heerdegen <at> web.de>
> Cc: 56423 <at> debbugs.gnu.org
> Date: Fri, 08 Jul 2022 14:57:34 +0200
> 
> Eli Zaretskii <eliz <at> gnu.org> writes:
> 
> > You mean, the display will no longer match the actual situation on
> > disk?  Then I think an unwind-protect or condition-case form that
> > resyncs the display in case of a signal is in order, since preventing
> > the user from aborting in that place would be wrong -- what if the
> > user realizes, too late, that some of the changes mean trouble?
> 
> The question is how to unwind.  I guess the only sensible action would
> be to revert the dired buffer, since we can't revert partial file
> changes, and the situation could look differently in many different
> ways.

Yes, I think reverting is TRT here, since (AFAIU) the display will
then reflect what was actually changed and what wasn't.

Previous Next

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