GNU bug report logs -
#64062
Emacs 29.0.91: With enable-recursive-minibuffers, C-x b foo splits the window.
Previous Next
To reply to this bug, email your comments to 64062 AT debbugs.gnu.org.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#64062
; Package
emacs
.
(Wed, 14 Jun 2023 10:36:02 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Alan Mackenzie <acm <at> muc.de>
:
New bug report received and forwarded. Copy sent to
bug-gnu-emacs <at> gnu.org
.
(Wed, 14 Jun 2023 10:36:02 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
In emacs-29.0.91:
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.
--
Alan Mackenzie (Nuremberg, Germany).
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#64062
; Package
emacs
.
(Wed, 14 Jun 2023 10:43:02 GMT)
Full text and
rfc822 format available.
Message #8 received at 64062 <at> debbugs.gnu.org (full text, mbox):
On Wed, Jun 14, 2023 at 10:35:07 +0000, Alan Mackenzie wrote:
> In emacs-29.0.91:
> emacs -Q
> M-: (setq enable-recursive-minibuffers t)
> M-x
> C-x b foo
Apologies: that last line should have read:
C-x b foo RET.
> 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.
> --
> Alan Mackenzie (Nuremberg, Germany).
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#64062
; Package
emacs
.
(Wed, 14 Jun 2023 10:59:01 GMT)
Full text and
rfc822 format available.
Message #11 received at 64062 <at> debbugs.gnu.org (full text, mbox):
>
> 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.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#64062
; Package
emacs
.
(Wed, 14 Jun 2023 11:47:02 GMT)
Full text and
rfc822 format available.
Message #14 received at 64062 <at> debbugs.gnu.org (full text, mbox):
> Cc: 64062 <at> debbugs.gnu.org
> Date: Wed, 14 Jun 2023 10:58:39 +0000
> From: Gregory Heytings <gregory <at> 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.
This bug report was last modified 1 year and 294 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.