unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Tino Calancha <tino.calancha@gmail.com>
Cc: 39138@debbugs.gnu.org
Subject: bug#39138: 28.0.50; Add variables for shell command output buffer names
Date: Wed, 15 Jan 2020 18:11:26 +0200	[thread overview]
Message-ID: <83v9pc4s41.fsf@gnu.org> (raw)
In-Reply-To: <878sm9u3m1.fsf@calancha-pc.dy.bbexcite.jp> (message from Tino Calancha on Tue, 14 Jan 2020 22:31:34 +0100)

> From: Tino Calancha <tino.calancha@gmail.com>
> Date: Tue, 14 Jan 2020 22:31:34 +0100
> 
> IMO, the two strings, `*Shell Command Output*' and
> `*Async Shell Command*', deserve variables with their docstrings.

Any rationale why we should add variables for these?  Who would want
to change the names, and why?

And even if we do provide such variables, I see no need to document
them in the manual.





  parent reply	other threads:[~2020-01-15 16:11 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 [this message]
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
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=83v9pc4s41.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=39138@debbugs.gnu.org \
    --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).