From: martin rudalics <rudalics@gmx.at>
To: Manuel Uberti <manuel.uberti@inventati.org>, 53189@debbugs.gnu.org
Subject: bug#53189: 29.0.50; Avoid window split in project-shell
Date: Tue, 11 Jan 2022 18:07:58 +0100 [thread overview]
Message-ID: <2d6a3c24-d4d7-d177-dd75-a8f9b4105cdc@gmx.at> (raw)
In-Reply-To: <bdd69de1-2403-da53-42ca-2c7417b06cbf@inventati.org>
> In order to avoid splitting the current window when I open a shell-mode buffer with `project-shell' I have this in my init.el:
>
> (setq-default display-buffer-alist '((".+shell*"
> (display-buffer-same-window)
> (reusable-frames . nil))))
>
> The first time I use `C-x p s` I am getting the behaviour I want. But if I do this:
>
> - `C-x p s`
> - `C-x b RET`
> - `C-x p s`
>
> The current window is split and the shell-mode buffer appears on the
> side.
>
> How can I avoid the window splitting?
This should be Bug#52878. Can you try with
diff --git a/lisp/window.el b/lisp/window.el
index 3f61d53128..068d76c87f 100644
--- a/lisp/window.el
+++ b/lisp/window.el
@@ -7474,9 +7474,10 @@ display-buffer-base-action
:version "24.1"
:group 'windows)
-(defcustom display-comint-buffer-action 'display-buffer-same-window
+(defcustom display-comint-buffer-action
+ '(display-buffer-same-window . ((inhibit-same-window . nil)))
"The action to display a comint buffer."
- :type display-buffer--action-function-custom-type
+ :type display-buffer--action-custom-type
:risky t
:version "29.1"
:group 'windows
Which also means that your customization is no more necessary.
martin
next prev parent reply other threads:[~2022-01-11 17:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-11 15:56 bug#53189: 29.0.50; Avoid window split in project-shell Manuel Uberti via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-11 17:07 ` martin rudalics [this message]
2022-01-11 18:24 ` Manuel Uberti via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-12 7:31 ` Manuel Uberti via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-08 13:59 ` Lars Ingebrigtsen
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=2d6a3c24-d4d7-d177-dd75-a8f9b4105cdc@gmx.at \
--to=rudalics@gmx.at \
--cc=53189@debbugs.gnu.org \
--cc=manuel.uberti@inventati.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.