From: Lars Ingebrigtsen <larsi@gnus.org>
To: Juri Linkov <juri@linkov.net>
Cc: Tino Calancha <tino.calancha@gmail.com>, 39138@debbugs.gnu.org
Subject: bug#39138: 28.0.50; Add variables for shell command output buffer names
Date: Mon, 10 Aug 2020 12:45:04 +0200 [thread overview]
Message-ID: <87d03y93v3.fsf@gnus.org> (raw)
In-Reply-To: <871rkf34cu.fsf@mail.linkov.net> (Juri Linkov's message of "Mon, 10 Aug 2020 02:18:41 +0300")
Juri Linkov <juri@linkov.net> writes:
> Oh, I noticed that the patch provided by Tino removed all mentions of
> shell buffer names from the documentation. While technically this is fine,
> I tried to look from the point of view of users, and realized that it's
> highly unlikely that the users might be interested to know the name of
> the constant 'shell-command-buffer-name', whereas it's very important
> for users to learn that the default name of the shell output buffer is
> "*Shell Command Output*".
I don't really see why? If the user is using one of these commands, of
course they'll see the buffer names themselves. If they're writing
code, they should be using 'shell-command-buffer-name', and not the
string "*Shell Command Output*".
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2020-08-10 10:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-14 21:31 bug#39138: 28.0.50; Add variables for shell command output buffer names Tino Calancha
2020-01-14 22:43 ` Michael Albinus
2020-01-15 8:03 ` Robert Pluim
2020-01-15 16:11 ` Eli Zaretskii
2020-01-15 19:41 ` Tino Calancha
2020-01-15 23:09 ` Juri Linkov
2020-02-25 13:12 ` Michael Albinus
2020-05-19 4:08 ` Stefan Kangas
2020-05-19 14:09 ` Eli Zaretskii
2020-05-19 14:16 ` Stefan Kangas
2020-05-19 15:26 ` Tino Calancha
2020-08-09 12:19 ` Lars Ingebrigtsen
2020-08-09 23:18 ` Juri Linkov
2020-08-10 10:45 ` Lars Ingebrigtsen [this message]
2020-08-10 23:59 ` Juri Linkov
2020-08-11 11:16 ` 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=87d03y93v3.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=39138@debbugs.gnu.org \
--cc=juri@linkov.net \
--cc=tino.calancha@gmail.com \
/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).