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

Previous Next

Full log

Message #41 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:22:11 +0300

> From: Michael Heerdegen <michael_heerdegen <at> web.de>
> Cc: 56423 <at> debbugs.gnu.org
> Date: Fri, 08 Jul 2022 14:04:22 +0200
> 
> Eli Zaretskii <eliz <at> gnu.org> writes:
> 
> > Yes, it's okay to inhibit-quit for short intervals of time and around
> > small code fragments.
> 
> The direction back (especially `wdired-finish-edit' after making many
> changes) is problematic however.  If the user aborts when file changes
> have been performed partly we have a problem I think.

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?

Previous Next

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