all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: <jakanakaevangeli@chiru.no>
To: sds@gnu.org, Lars Ingebrigtsen <larsi@gnus.org>
Cc: Stefan Kangas <stefan@marxist.se>,
	Theodor Thornhill <theo@thornhill.no>,
	52467@debbugs.gnu.org, Dmitry Gutov <dgutov@yandex.ru>
Subject: bug#52467: 29.0.50; Use pop-to-buffer for shell
Date: Mon, 27 Dec 2021 10:32:13 +0100	[thread overview]
Message-ID: <87zgomieaq.fsf@miha-pc> (raw)
In-Reply-To: <87v8zb2tdz.fsf@gnu.org>

Sam Steingold <sds@gnu.org> writes:

> I think predictability if not the only or even main concern.
>
> The current behavior is _not_ user-customizable, which is a major
> problem for me. I hardly ever want the same buffer displayed _twice_,
> especially the *shell* buffer.
>
> Whatever default behavior you want (and for me it's definitely
> reuse-window) should be implemented using a new user variable
> `shell-display-buffer-action' that would be used by `shell',
> `project-shell', `eshell', &c.

It is user configurable through 'display-buffer-alist, see my other
reply to this thread. To prevent creation of duplicate windows showing
the same shell buffer, do

   (add-to-list 'display-buffer-alist
                '("\\`\\*shell\\*" display-buffer-reuse-window))

For old behaviour of popping up a new shell window, do

   (add-to-list 'display-buffer-alist
                '("\\`\\*shell\\*"
                  (display-buffer-reuse-window display-buffer-pop-up-window)))

The same can be done for eshell, terminal and most other buffers
displayed with 'display-buffer-same-window'.

> This is not a major change, so I propose that we close this bug by
> adding `shell-display-buffer-action' (I can do that), and continue the
> discussion of the best default on emacs-devel.

I'm personally against adding such an user option.

If it were added for M-x shell, eshell and term, the same reasoning
could be used to add it for M-x run-scheme, dired, dunnet and all the
other places using 'pop-to-buffer-same-window'. This would add up to a
lot of variables for little benefit since we can already customize
window pop-up behaviour of all these commands with
'display-buffer-alist'.

> Thank you.





  reply	other threads:[~2021-12-27  9:32 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-13 16:16 bug#52467: 29.0.50; Use pop-to-buffer for shell Steingold
2021-12-13 21:14 ` Dmitry Gutov
2021-12-14  8:19   ` Theodor Thornhill via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-12-19 13:14   ` Lars Ingebrigtsen
2021-12-19 23:34     ` Dmitry Gutov
     [not found]       ` <CADwFkm=60K=ttDtK+z5v1Ch=qDUbng42jkyzV-7vLeC8zKLq6A@mail.gmail.com>
2021-12-20 10:17         ` Lars Ingebrigtsen
2021-12-24  0:38           ` Sam Steingold
2021-12-24  0:51           ` Dmitry Gutov
2021-12-24  9:07             ` Lars Ingebrigtsen
2021-12-26  0:47               ` Dmitry Gutov
2021-12-26 11:35                 ` Lars Ingebrigtsen
2021-12-26 15:37                   ` Dmitry Gutov
2021-12-26 17:00                   ` Sam Steingold
2021-12-27  9:32                     ` jakanakaevangeli [this message]
2021-12-27 12:01                       ` Lars Ingebrigtsen
2021-12-14 15:59 ` jakanakaevangeli

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=87zgomieaq.fsf@miha-pc \
    --to=jakanakaevangeli@chiru.no \
    --cc=52467@debbugs.gnu.org \
    --cc=dgutov@yandex.ru \
    --cc=larsi@gnus.org \
    --cc=sds@gnu.org \
    --cc=stefan@marxist.se \
    --cc=theo@thornhill.no \
    /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.