unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, Drew Adams <drew.adams@oracle.com>
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: Fri, 1 Nov 2019 14:34:59 -0700 (PDT)	[thread overview]
Message-ID: <bf5ebdb6-f2b9-4e77-ab5f-7f31bee8681f@default> (raw)
In-Reply-To: <<83y2wzjnm5.fsf@gnu.org>>

> > I take it back that no other bug mails show the
> > problem.  Just got the attached mail from Stefan K.,
> > which shows the same problem - no bug # in Subject
> > field.
> 
> FWIW, I do see the bug number in Subject of that message.

Interesting.  I assume you mean the message that I
included as an attachment.  Odd that I don't see the bug
number there.

What's more, if I open that message in its own (Outlook)
window and use "File > Properties", the field "Internet
headers" is completely empty.  Normally that field shows
the full email header.





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

  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=bf5ebdb6-f2b9-4e77-ab5f-7f31bee8681f@default \
    --to=drew.adams@oracle.com \
    --cc=14659@debbugs.gnu.org \
    --cc=eliz@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).