GNU bug report logs - #70819
29.3; clone-indirect-buffer-other-window is inconsistent with *-other-window commands

Previous Next

Full log

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

From: Eli Zaretskii <eliz <at> gnu.org>
To: Richard Sent <richard <at> freakingpenguin.com>
Cc: rudalics <at> gmx.at, 70819 <at> debbugs.gnu.org, monnier <at> iro.umontreal.ca
Subject: Re: [PATCH] Make clone-indirect-buffer-other-window use other window
Date: Mon, 13 May 2024 08:22:27 +0300

> From: Richard Sent <richard <at> freakingpenguin.com>
> Cc: Eli Zaretskii <eliz <at> gnu.org>,  martin rudalics <rudalics <at> gmx.at>,
>   70819 <at> debbugs.gnu.org
> Date: Sun, 12 May 2024 23:14:19 -0400
> 
> Previously, depending on the settings in display-buffer-alist,
> clone-indirect-buffer-other-window would display the cloned buffer in
> the original window, behaving identically to clone-indirect-buffer with
> a non-nil display-flag. This behavior was inconsistent with other-window
> commands, which always used another window.
> 
> Now, clone-indirect-buffer-other-window uses
> switch-to-buffer-other-window. This means it uses the same logic as
> other-window commands like find-file-other-window and info-other-window
> and its behavior is more consistent.
> 
> Because there is no reason for an other-window command to take a
> display-flag argument, the argument was removed.

Thanks, but we cannot change an API of a public function.  We must
keep the argument, but not use it (and a NEWS entry should say that it
is now unused).

Previous Next

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