unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 14659@debbugs.gnu.org
Subject: bug#14659: 24.3.50; `modify-frame-parameters' raises error for font returned by `xs-list-fonts'
Date: Fri, 1 Nov 2019 11:22:02 -0700 (PDT)	[thread overview]
Message-ID: <fa4a2a19-2888-418d-918c-254721679808@default> (raw)
In-Reply-To: <87eeyrwl9t.fsf@gnus.org>

BTW, this and other bug mails from you today is missing the bug number from the Subject line.

The bug number was present in the cc to 14659@debbugs.gnu.org, so my Reply All resulted in the reply going to that cc address, so I received a copy of my reply with the bug #.

But the message from you that I replied to had only this as Subject:

  RE: 24.3.50; `modify-frame-parameters' raises error for font returned by `xs-list-fonts'

That makes it very hard (~impossible) to search or sort by Subject line in my mail client (Outlook).  Could you please make sure that the bug number remains in the Subject line when you reply?

For some reason, I saw this for multiple bug mails from you today, but not from others.  I don't think I've seen it before.

Thx.





  parent reply	other threads:[~2019-11-01 18:22 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>
2013-06-18 21:26       ` bug#14659: 24.3.50; `modify-frame-parameters' raises error for font returned by `xs-list-fonts' 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 [this message]
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
     [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           ` 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

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=fa4a2a19-2888-418d-918c-254721679808@default \
    --to=drew.adams@oracle.com \
    --cc=14659@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    /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).