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 #76 received at 27243 <at> debbugs.gnu.org (full text, mbox):

From: martin rudalics <rudalics <at> gmx.at>
To: Eli Zaretskii <eliz <at> gnu.org>, Stephen Berman <stephen.berman <at> gmx.net>
Cc: 27243 <at> debbugs.gnu.org, antoine.levitt <at> gmail.com
Subject: Re: bug#27243: another case: dired-auto-revert-buffer jumps point
 to beginning of buffer
Date: Sun, 23 Jul 2017 20:40:53 +0200
> Martin, when might pop-to-buffer-same-window show the buffer in a
> window other than the selected one?  If we are going to make this
> change, we need first to understand when it might misfire, because
> some users of find-file might not like the situation where the buffer
> pops up in another window.

Conceptually both, ‘pop-to-buffer-same-window’ and ‘switch-to-buffer’,
behave alike in this regard: They avoid the minibuffer and windows
strongly dedicated to their buffers.  Interactively, ‘switch-to-buffer’
may show another buffer in a strongly dedicated window when the option
‘switch-to-buffer-in-dedicated-window’ is non-nil, but I suppose the
issues mentioned in this thread are not about the interactive use of
‘switch-to-buffer’.

> E.g., what happens in this particular use case if the Dire4d buffer
> pops in another window?

If the dired buffer was earlier shown by ‘switch-to-buffer’ and is now
shown by ‘pop-to-buffer-same-window’, the behaviors should be the same.
Quitting the dired window, however, may behave differently.

martin





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

Previous Next


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