[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#70819: [PATCH v2] Make clone-indirect-buffer-other-window use other
From: |
Eli Zaretskii |
Subject: |
bug#70819: [PATCH v2] Make clone-indirect-buffer-other-window use other window (bug#70819) |
Date: |
Sat, 08 Jun 2024 15:18:51 +0300 |
> From: Richard Sent <richard@freakingpenguin.com>
> Cc: rudalics@gmx.at,
> eliz@gnu.org,
> Richard Sent <richard@freakingpenguin.com>
> Date: Mon, 27 May 2024 11:32:00 -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.
>
> display-flag was kept for API stability and functional compatibility
> reasons.
>
> * lisp/simple.el: (clone-indirect-buffer-other-window): Use
> switch-to-buffer-other-window.
Thanks, installed on master, and closing the bug.
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- bug#70819: [PATCH v2] Make clone-indirect-buffer-other-window use other window (bug#70819),
Eli Zaretskii <=