From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Kangas <stefan@marxist.se>
Cc: larsi@gnus.org, 14659@debbugs.gnu.org
Subject: bug#14659: 24.3.50; `modify-frame-parameters' raises error for font returned by `xs-list-fonts'
Date: Sat, 02 Nov 2019 10:42:32 +0200 [thread overview]
Message-ID: <83a79ek6tj.fsf@gnu.org> (raw)
In-Reply-To: <CADwFkmkayqziW__AyjQH4ZPh-tVG=6s9TeS+U3SkO=uP-zpSSA@mail.gmail.com> (message from Stefan Kangas on Sat, 2 Nov 2019 08:26:49 +0100)
> From: Stefan Kangas <stefan@marxist.se>
> Date: Sat, 2 Nov 2019 08:26:49 +0100
> Cc: Drew Adams <drew.adams@oracle.com>, Lars Ingebrigtsen <larsi@gnus.org>, 14659@debbugs.gnu.org
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > > Interesting. I assume you mean the message that I
> > > included as an attachment.
> >
> > No, I mean that same message that I received directly from the bug
> > tracker. The copy you attached indeed didn't include the bug number.
>
> If I'm not mistaken, I believe what Lars said is correct -- the
> problem is that debbugs currently doesn't include the bug number in
> the subject line due to the recent change in
> gnus-bug-group-download-format-alist. When you're in "To:" or "Cc:",
> the subject line will therefore not include the bug number, which is
> what Drew is seeing. If you instead receive the same email only from
> the list, the bug number was added back automatically by the list
> software before it was distributed.
I was just reporting my observations.
next prev parent reply other threads:[~2019-11-02 8:42 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<<afadb85f-976f-45c0-9c06-6471a95c4c80@default>
[not found] ` <<<87eeyrwl9t.fsf@gnus.org>
[not found] ` <<<fa4a2a19-2888-418d-918c-254721679808@default>
[not found] ` <<<83eeyrl8h0.fsf@gnu.org>
[not found] ` <<f89b06c1-e96f-4eea-af6b-f1355a9af803@default>
[not found] ` <<83y2wzjnm5.fsf@gnu.org>
2019-11-01 21:34 ` bug#14659: 24.3.50; `modify-frame-parameters' raises error for font returned by `xs-list-fonts' Drew Adams
2019-11-01 22:16 ` Stefan Kangas
2019-11-01 22:23 ` Drew Adams
2019-11-01 22:56 ` Stephen Berman
2019-11-01 23:07 ` Drew Adams
2019-11-01 23:05 ` Lars Ingebrigtsen
2019-11-01 23:12 ` Drew Adams
2019-11-02 14:57 ` Lars Ingebrigtsen
2019-11-02 7:01 ` Eli Zaretskii
2019-11-02 7:26 ` Stefan Kangas
2019-11-02 8:42 ` Eli Zaretskii [this message]
[not found] <<afadb85f-976f-45c0-9c06-6471a95c4c80@default>
[not found] ` <<87eeyrwl9t.fsf@gnus.org>
[not found] ` <<fa4a2a19-2888-418d-918c-254721679808@default>
[not found] ` <<83eeyrl8h0.fsf@gnu.org>
2013-06-18 21:26 ` Drew Adams
2019-11-01 17:37 ` Lars Ingebrigtsen
2019-11-01 18:04 ` Drew Adams
2019-11-02 14:38 ` Lars Ingebrigtsen
2019-11-01 18:22 ` Drew Adams
2019-11-01 19:09 ` Eli Zaretskii
2019-11-01 21:11 ` Drew Adams
2019-11-01 21:25 ` Eli Zaretskii
2019-11-01 21:02 ` Drew Adams
2019-11-03 3:24 ` Richard Stallman
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83a79ek6tj.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=14659@debbugs.gnu.org \
--cc=larsi@gnus.org \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.