From: Sam Steingold <sds@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 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: Thu, 23 Dec 2021 19:38:31 -0500 [thread overview]
Message-ID: <87zgoq3khk.fsf@gnu.org> (raw)
In-Reply-To: <87wnjzoa09.fsf@gnus.org> (Lars Ingebrigtsen's message of "Mon, 20 Dec 2021 11:17:58 +0100")
At this time the current behavior in unpalatable in that I sometimes get
a second window with the same buffer, and there is no way for me to
change it.
Wouldn't it be better to at least use `pop-to-buffer' everywhere and
let the user decide what they prefer using the standard mechanisms like
`display-buffer-base-action' or `display-buffer-alist'?
Thank you!
--
Sam Steingold (http://sds.podval.org/) on Pop 21.10 (impish) X 11.0.12013000
http://childpsy.net http://calmchildstories.com http://steingoldpsychology.com
https://iris.org.il http://think-israel.org https://memri.org
Bug free software merely has random features.
next prev parent reply other threads:[~2021-12-24 0:38 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 [this message]
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=87zgoq3khk.fsf@gnu.org \
--to=sds@gnu.org \
--cc=52467@debbugs.gnu.org \
--cc=dgutov@yandex.ru \
--cc=larsi@gnus.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).