From: Manuel Uberti via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: martin rudalics <rudalics@gmx.at>, 53189@debbugs.gnu.org
Subject: bug#53189: 29.0.50; Avoid window split in project-shell
Date: Tue, 11 Jan 2022 19:24:26 +0100 [thread overview]
Message-ID: <33e6381c-1aee-cf4c-2250-3160b9ff9458@inventati.org> (raw)
In-Reply-To: <2d6a3c24-d4d7-d177-dd75-a8f9b4105cdc@gmx.at>
On 11/01/22 18:07, martin rudalics wrote:
> 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.
I built master on commit c8ea3f09e09b18b909f5a6c5434185b8dbf2fa63 (which comes
after 4765487d5d24fc8a2a06c329dc9cc3bed9803391, on which I see a similar change
to what you proposed), removed my customization, but the problem remains.
--
Manuel Uberti
www.manueluberti.eu
next prev parent reply other threads:[~2022-01-11 18:24 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
2022-01-11 18:24 ` Manuel Uberti via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
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
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=33e6381c-1aee-cf4c-2250-3160b9ff9458@inventati.org \
--to=bug-gnu-emacs@gnu.org \
--cc=53189@debbugs.gnu.org \
--cc=manuel.uberti@inventati.org \
--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).