From: Lars Ingebrigtsen <larsi@gnus.org>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: 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, 19 Dec 2021 14:14:02 +0100 [thread overview]
Message-ID: <87sfuorb39.fsf@gnus.org> (raw)
In-Reply-To: <fa35092f-5e8f-369a-08f3-6987097e6d4c@yandex.ru> (Dmitry Gutov's message of "Tue, 14 Dec 2021 00:14:31 +0300")
Dmitry Gutov <dgutov@yandex.ru> writes:
> On 13.12.2021 19:16, Steingold wrote:
>> It seems much more reasonable to use pop-to-buffer in eshell rather than
>> break shell's behavior.
>
> That seems reasonable too.
>
> I think we'll do whatever the maintainers decide on this issue.
I think the current behaviour makes more sense than the old one, really.
For one, it's more predictable -- when you say `M-x shell', you're
getting a shell in the current buffer. The old behaviour either does
that, or lands you in a different window (if you've already got a shell
buffer open elsewhere), right?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2021-12-19 13:14 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 [this message]
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
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=87sfuorb39.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=52467@debbugs.gnu.org \
--cc=dgutov@yandex.ru \
--cc=sds@gnu.org \
--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).