unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Dmitry Gutov <dgutov@yandex.ru>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Stefan Kangas <stefan@marxist.se>,
	sds@gnu.org, Theodor Thornhill <theo@thornhill.no>,
	52467@debbugs.gnu.org
Subject: bug#52467: 29.0.50; Use pop-to-buffer for shell
Date: Sun, 26 Dec 2021 02:47:59 +0200	[thread overview]
Message-ID: <ac6b4c44-a1e9-f433-35e7-61f3c8437204@yandex.ru> (raw)
In-Reply-To: <87h7ay4bhg.fsf@gnus.org>

On 24.12.2021 12:07, Lars Ingebrigtsen wrote:
> What is that you propose should change?

Basically what Sam is asking (use pop-to-window for both shell and 
eshell), I'm just trying to conceptualize that change. Not a strong 
preference, but it seems to make sense.

Or to approach the question from another angle, the difference between 
that behavior and the current one is that you can create two windows 
that show the same buffer. Do we want that to happen with 'M-x shell' 
without prefix?

Overall, pop-to-buffer seems more common than pop-to-buffer-same-window.

The downside of using it, though, is that the current window is unlikely 
to be used even if the buffer is not displayed anywhere else (the 
algorithm chooses something like LRU window). Maybe we should choose a 
mode of operation where it does use the current window, unless the 
buffer is displayed somewhere else.

Something like

     (pop-to-buffer buffer
                    '((display-buffer-reuse-window
                       display-buffer-same-window)
                      (inhibit-same-window . nil)))





  reply	other threads:[~2021-12-26  0:47 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 [this message]
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
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

  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=ac6b4c44-a1e9-f433-35e7-61f3c8437204@yandex.ru \
    --to=dgutov@yandex.ru \
    --cc=52467@debbugs.gnu.org \
    --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 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).