From: Tino Calancha <tino.calancha@gmail.com>
To: Stefan Kangas <stefan@marxist.se>
Cc: tino.calancha@gmail.com, michael.albinus@gmx.de, 39138@debbugs.gnu.org
Subject: bug#39138: 28.0.50; Add variables for shell command output buffer names
Date: Tue, 19 May 2020 17:26:43 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.21.2005191719460.9286@calancha-pc.dy.bbexcite.jp> (raw)
In-Reply-To: <CADwFkm=dCpcmXmcEyYGwdJdjk9V497TLbNtHw-p_m=teaEqv3g@mail.gmail.com>
On Tue, 19 May 2020, Stefan Kangas wrote:
> Eli Zaretskii <eliz@gnu.org> writes:
>
>>> This seems to have stalled. Is anyone still interested in this change,
>>> or should the bug be closed?
>>
>> It sounds like the best consensus we could have is to make defconsts
>> out of these strings, to avoid having many identical copies of them.
>
> Right. Tino, could you take a look at that and see if it makes sense to
> send an updated patch?
TBH, I am not that much interested in this change (even if I opened it).
Since yesterday I am again w/ bug#39121 which provides more value.
Also, I have in my TODO list to open a bug for `iconify-frame', which
gives me some problems in one of my laptops (under investigation).
Please, feel free to get ownership of the present bug if you find it
useful, or close it as won't fix.
next prev parent reply other threads:[~2020-05-19 15:26 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 [this message]
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=alpine.DEB.2.21.2005191719460.9286@calancha-pc.dy.bbexcite.jp \
--to=tino.calancha@gmail.com \
--cc=39138@debbugs.gnu.org \
--cc=michael.albinus@gmx.de \
--cc=stefan@marxist.se \
/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).