unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Richard Sent <richard@freakingpenguin.com>
Cc: rudalics@gmx.at, 70819@debbugs.gnu.org, monnier@iro.umontreal.ca
Subject: bug#70819: [PATCH] Make clone-indirect-buffer-other-window use other window
Date: Mon, 13 May 2024 08:22:27 +0300	[thread overview]
Message-ID: <86y18exp4c.fsf@gnu.org> (raw)
In-Reply-To: <87v83ipfn8.fsf_-_@freakingpenguin.com> (message from Richard Sent on Sun, 12 May 2024 23:14:19 -0400)

> From: Richard Sent <richard@freakingpenguin.com>
> Cc: Eli Zaretskii <eliz@gnu.org>,  martin rudalics <rudalics@gmx.at>,
>   70819@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).





  reply	other threads:[~2024-05-13  5:22 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-07 16:19 bug#70819: 29.3; clone-indirect-buffer-other-window is inconsistent with *-other-window commands Richard Sent
2024-05-11  9:29 ` Eli Zaretskii
2024-05-12  8:30   ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-13  2:26   ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-13  3:14     ` bug#70819: [PATCH] Make clone-indirect-buffer-other-window use other window Richard Sent
2024-05-13  5:22       ` Eli Zaretskii [this message]
2024-05-13  8:05       ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-25  7:49         ` Eli Zaretskii
2024-06-08 11:45           ` Eli Zaretskii
2024-06-08 13:29             ` Eli Zaretskii
2024-05-27 15:32 ` bug#70819: [PATCH v2] Make clone-indirect-buffer-other-window use other window (bug#70819) Richard Sent
2024-05-28  8:04   ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-08 12:18   ` Eli Zaretskii

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=86y18exp4c.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=70819@debbugs.gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=richard@freakingpenguin.com \
    --cc=rudalics@gmx.at \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).