Subject: bug#75626: 31.0.50; Dired misses or double-processes files when auto-revert-mode is enabled

From: Michael Heerdegen <[email-masked]>
Date: Sun, 19 Jan 2025 03:05:57 +0100

Tassilo Horn <[email-masked]> writes:

> What is the reason that there are two different approaches to process
> all marked files, i.e., dired-map-over-marks vs. dired-get-marked-files?

It could be that it is just a historical coincidence.

The question than would be if we want to reimplement the command, or if
we try to make it (more) robust.

We could, for example, remember the current position as a marker instead
of a number, and/or try to prevent auto revert while the command is
processed.  AFAIU, `dired-buffer-stale-p' could be changed to return nil
in this case to prevent reverting.  Or would binding
dired-auto-revert-buffer -> nil already be enough?

Michael.