GNU bug report logs - #27243
dired-auto-revert-buffer jumps point to beginning of buffer

Previous Next

Package: emacs;

Reported by: Antoine Levitt <antoine.levitt <at> gmail.com>

Date: Sun, 4 Jun 2017 23:46:01 UTC

Severity: normal

Done: Eli Zaretskii <eliz <at> gnu.org>

Bug is archived. No further changes may be made.

Full log


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

From: Michael Heerdegen <michael_heerdegen <at> web.de>
To: Stephen Berman <stephen.berman <at> gmx.net>
Cc: martin rudalics <rudalics <at> gmx.at>, Eli Zaretskii <eliz <at> gnu.org>,
 antoine.levitt <at> gmail.com, monnier <at> IRO.UMontreal.CA, 27243 <at> debbugs.gnu.org
Subject: Re: bug#27243: another case: dired-auto-revert-buffer jumps point
 to beginning of buffer
Date: Wed, 27 May 2020 03:23:05 +0200
Stephen Berman <stephen.berman <at> gmx.net> writes:

> 1. emacs -Q
> 2. M-: switch-to-buffer-preserve-window-point RET => t
>    M-: dired-auto-revert-buffer RET => nil
> 3. C-x d RET M-: (point) => 211
> 4. C-x 2 C-x o 10 n M-: (point) => 890
> 5. C-x o ^ RET M-: (point) => 211
> also: 6. C-x o ^ RET M-: (point) => 890

But if I do this with emacs -Q, and use edebug to step through the
related functions, I can reproduce it there.  It is enough to edebug
just `dired-find-file' and hit SPC, SPC ... for the issue to occur as I
see it.

I was using two different frames for Edebugging and performing the
recipe.

Does this confirm my suspicions that intermediate redisplay may play a
role?

Michael.




This bug report was last modified 4 years and 358 days ago.

Previous Next


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