From: martin rudalics via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Richard Sent <richard@freakingpenguin.com>, 70819@debbugs.gnu.org
Cc: eliz@gnu.org
Subject: bug#70819: [PATCH v2] Make clone-indirect-buffer-other-window use other window (bug#70819)
Date: Tue, 28 May 2024 10:04:19 +0200 [thread overview]
Message-ID: <d49bc58b-af60-4f5a-9cf6-cb5c711a957f@gmx.at> (raw)
In-Reply-To: <20240527153341.26919-1-richard@freakingpenguin.com>
> - (let ((pop-up-windows t))
> - (clone-indirect-buffer newname display-flag norecord)))
> + ;; For compatibility, don't display the buffer if display-flag is nil.
> + (let ((buffer (clone-indirect-buffer newname nil norecord)))
> + (when display-flag
> + (switch-to-buffer-other-window buffer norecord))))
Looks good to me.
Thank you, martin
next prev parent reply other threads:[~2024-05-28 8:04 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d49bc58b-af60-4f5a-9cf6-cb5c711a957f@gmx.at \
--to=bug-gnu-emacs@gnu.org \
--cc=70819@debbugs.gnu.org \
--cc=eliz@gnu.org \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.