From: Eli Zaretskii <eliz@gnu.org>
To: Gregory Heytings <gregory@heytings.org>
Cc: acm@muc.de, 64062@debbugs.gnu.org
Subject: bug#64062: Emacs 29.0.91: With enable-recursive-minibuffers, C-x b foo splits the window.
Date: Wed, 14 Jun 2023 14:46:29 +0300 [thread overview]
Message-ID: <83o7liuuzu.fsf@gnu.org> (raw)
In-Reply-To: <42ff58c7e86104bcce30@heytings.org> (message from Gregory Heytings on Wed, 14 Jun 2023 10:58:39 +0000)
> Cc: 64062@debbugs.gnu.org
> Date: Wed, 14 Jun 2023 10:58:39 +0000
> From: Gregory Heytings <gregory@heytings.org>
>
> > emacs -Q
> > M-: (setq enable-recursive-minibuffers t)
> > M-x
> > C-x b foo
> >
> > This creates the buffer foo, but erroneously splits the displayed window
> > and displays the new buffer in the right hand or bottom half of the
> > frame (depending on the frame's geometry).
> >
> > The window should not be split, and the new buffer should occupy the
> > entirety of the original window.
>
> AFAICS, that's not a bug. Emacs 25, 26, 27 and 28 behave the same
> (switch-to-buffer calls pop-to-buffer), and it makes sense to leave, by
> default, the buffer in which M-x was called visible. You can customize
> that behavior with display-buffer-base-action.
Indeed, I don't think this long-time behavior is a bug. It's more
like a feature.
prev parent reply other threads:[~2023-06-14 11:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-14 10:35 bug#64062: Emacs 29.0.91: With enable-recursive-minibuffers, C-x b foo splits the window Alan Mackenzie
2023-06-14 10:42 ` Alan Mackenzie
2023-06-14 10:58 ` Gregory Heytings
2023-06-14 11:46 ` Eli Zaretskii [this message]
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=83o7liuuzu.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=64062@debbugs.gnu.org \
--cc=acm@muc.de \
--cc=gregory@heytings.org \
/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.