GNU bug report logs - #75626
31.0.50; Dired misses or double-processes files when auto-revert-mode is enabled

Previous Next

Package: emacs;

Reported by: Tassilo Horn <tsdh <at> gnu.org>

Date: Fri, 17 Jan 2025 07:43:01 UTC

Severity: normal

Found in version 31.0.50

Done: Tassilo Horn <tsdh <at> gnu.org>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: Tassilo Horn <tsdh <at> gnu.org>
To: Drew Adams <drew.adams <at> oracle.com>
Cc: Michael Heerdegen <michael_heerdegen <at> web.de>, "75626 <at> debbugs.gnu.org" <75626 <at> debbugs.gnu.org>, Eli Zaretskii <eliz <at> gnu.org>
Subject: bug#75626: 31.0.50; Dired misses or double-processes files when auto-revert-mode is enabled
Date: Mon, 20 Jan 2025 07:13:48 +0100
Drew Adams <drew.adams <at> oracle.com> writes:

> Still not following this thread.  But if the plan
> is to make `dired-map-over-marks' prevent things
> such as reverting, then a priori I'm not in favor
> of that.  A priori, I think that macro should
> implement no such control, and make _few or no
> assumptions_ about the context in which it's used
> or the purposes to which it might be put to use.
> Such control is not its role.
>
> If some particular _use_ of the macro should
> provide some such control, e.g., should not let
> XYZ happen, then fix that function instead (even
> if that might mean not using the macro there).
>
> The macro itself should stay general & unassuming.

The plan is to change dired-buffer-stale-p so that it returns nil when
inhibit-read-only is bound to a non-nil value which is the case during
the execution of the code generated by dired-map-over-marks and might
catch other cases, too.  The macro itself stays as-is.

Bye,
Tassilo




This bug report was last modified 196 days ago.

Previous Next


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