bug#71264: 30.0.50; Dired deletion moves point under auto-revert

[Manuel Giraud]

Hi Basil,

I think I'm onto something regarding this bug.  We can observe the same
misbehavior with the following patch:

diff --git a/lisp/dired.el b/lisp/dired.el
index f2a75df6ef1..325c61627c2 100644
--- a/lisp/dired.el
+++ b/lisp/dired.el
@@ -4100,9 +4100,7 @@ dired-clean-up-after-deletion
     (let ((buf (get-file-buffer fn)))
       (and buf
            (or (and dired-clean-confirm-killing-deleted-buffers
-                    (funcall #'y-or-n-p
-                             (format "Kill buffer of %s, too? "
-                                     (file-name-nondirectory fn))))
+                    (sit-for 0.3))
                (not dired-clean-confirm-killing-deleted-buffers))
            (kill-buffer buf)))
     (let ((buf-list (dired-buffers-for-dir-or-subdir

It seems to me that the 'y-or-n-p' call gives the opportunity of a time
window for the dired buffer to be reverted.  But then, when this revert
happen the file "foo" has already disappeared so it cannot be found and
the point ends up at the BOB.

I don't know how to prevent this yet.
-- 
Manuel Giraud