Subject: bug#70819: [PATCH] Make clone-indirect-buffer-other-window use other window

From: Eli Zaretskii <[email-masked]>
Date: Mon, 13 May 2024 08:22:27 +0300

> From: Richard Sent <[email-masked]>
> Cc: Eli Zaretskii <[email-masked]>,  martin rudalics <[email-masked]>,
>   [email-masked]
> 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).