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

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

[Drew Adams]

Not sure there is a bug here, but I think so.

(x-list-fonts "*") returns a list containing this XLFD font name
(and two other names that are similar):
"-outline-DFKai-SB-normal-normal-normal-script-*-*-*-*-c-*-iso8859-1".

That is not a valid XFLD name (e.g., it contains 15, not 14, hyphens).
And this error is raised by `modify-frame-parameters':

Debugger entered--Lisp error: (error "Font `-outline-DFKai-SB-normal-normal-normal-script-*-*-*-*-c-*-iso8859-1' is not defined")
  modify-frame-parameters(#<frame throw-i-font.el 06b50270> ((font . "-outline-DFKai-SB-normal-normal-normal-script-*-*-*-*-c-*-iso8859-1")))

Should `xs-list-fonts' return only valid XFLD font names?  Or is the
current behavior correct on all counts?

Note that I can use this font otherwise.  E.g., in emacs -Q I can
S-mouse-1, `Change Buffer Font', choose `DFKai-SB', and the font is
used OK.  That uses `x-select-font'.  So perhaps the bug is with
`modify-frame-parameters' (?).

In GNU Emacs 24.3.50.1 (i686-pc-mingw32)
 of 2013-06-17 on ODIEONE
Bzr revision: 113024 eliz@gnu.org-20130617163040-8hmzci370q4argze
Windowing system distributor `Microsoft Corp.', version 6.1.7601
Configured using:
 `configure --prefix=/c/Devel/emacs/binary --enable-checking=yes,glyphs
 CFLAGS=-O0 -g3 LDFLAGS=-Lc:/Devel/emacs/lib
 CPPFLAGS=-Ic:/Devel/emacs/include'

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

[Lars Ingebrigtsen]

Drew Adams <drew.adams@oracle.com> writes:

> Not sure there is a bug here, but I think so.
>
> (x-list-fonts "*") returns a list containing this XLFD font name
> (and two other names that are similar):
> "-outline-DFKai-SB-normal-normal-normal-script-*-*-*-*-c-*-iso8859-1".
>
> That is not a valid XFLD name (e.g., it contains 15, not 14, hyphens).

I tried this on this Debian laptop:

(loop for font in (x-list-fonts "*")
      unless (= (loop for char across font
		   when (= char ?-)
		   sum 1)
		14)
      do (insert font "\n"))

and there were no fonts returned by the function that's invalid in this
way.  I don't know whether that's because I just don't have any such
font, or whether x-list-fonts has been fixed not to return these invalid
font strings.

Are you still seeing this?

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no

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

[Drew Adams]

> Are you still seeing this?

No, but I no longer have that font installed.
I no longer have the same laptop etc...

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

[Lars Ingebrigtsen]

Drew Adams <drew.adams@oracle.com> writes:

>> Are you still seeing this?
>
> No, but I no longer have that font installed.
> I no longer have the same laptop etc...

OK, then it seems unlikely that we'll make further progress here, and
I'm closing this bug report.  Please reopen if you see this again.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no

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

[Drew Adams]

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.

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

[Eli Zaretskii]

> Date: Fri, 1 Nov 2019 11:22:02 -0700 (PDT)
> From: Drew Adams <drew.adams@oracle.com>
> Cc: 14659@debbugs.gnu.org
> 
> BTW, this and other bug mails from you today is missing the bug number from the Subject line.

They are not missing here.

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

[Drew Adams]

[-- Attachment #1: Type: text/plain, Size: 684 bytes --]

> And other bug mails are not missing the bug number
> from the Subject line.
> 
> And even Lars's mails from other days were not
> missing bug numbers from the Subject line.  Maybe
> it's only these few bugs; dunno.

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.

I haven't changed anything on my end.  And this
problem is new.  Previously, the Subject line always
appeared as does this one now: with bug#...: followed
by the release number - not just starting with the
release number (no bug #):

  RE: bug#14659: 24.3.50; `modify-frame-parameters'...

[-- Attachment #2: Type: message/rfc822, Size: 1371 bytes --]

From: Stefan Kangas <stefan@marxist.se>
To: Drew Adams <drew.adams@oracle.com>
Cc: 11314@debbugs.gnu.org
Subject: Re: 24.1.50; Regression: incorrect Lisp indentation for `if' with `@@@@@@'
Date: Fri, 1 Nov 2019 12:59:15 -0700 (PDT)
Message-ID: <87imo3xt9o.fsf@marxist.se>

found 11314 27.0.50
thanks

"Drew Adams" <drew.adams@oracle.com> writes:

> emacs -Q
>  
> Type this into an Emacs Lisp buffer:
>  
> (if (alpha beta) C-j aaaaaa C-j bbbbbb
>  
> You get this:
>  
> (if (alpha beta)
>     aaaaaa
>   bbbbbb
>  
> That is correct.  bbbbbb is indented correctly.
>  
> Now do the same thing, using @@@@@@ instead of aaaaaa.  This is the
> result - bbbbbb is indented incorrectly.
>  
> (if (alpha beta)
>     @@@@@@
>     bbbbbb
>  
> Yet @@@@@@ is a perfectly good symbol/variable name etc.
>  
> This regression was introduced in Emacs 22.

I can reproduce this on current master.

Best regards,
Stefan Kangas

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

[Eli Zaretskii]

> Date: Fri, 1 Nov 2019 14:11:07 -0700 (PDT)
> From: Drew Adams <drew.adams@oracle.com>
> Cc: larsi@gnus.org, 14659@debbugs.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.

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

[Drew Adams]

> > BTW, this and other bug mails from you today is missing the bug
> > number from the Subject line.
> 
> They are not missing here.

They are missing here.  My mail client is Outlook.

And other bug mails are not missing the bug number
from the Subject line.

And even Lars's mails from other days were not
missing bug numbers from the Subject line.  Maybe
it's only these few bugs; dunno.

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

[Richard Stallman]

[[[ To any NSA and FBI agents reading my email: please consider    ]]]
[[[ whether defending the US Constitution against all enemies,     ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]

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

The FSF sysadmins said during the week that they had changed how RT
lists forward mail.  I did not follow the details, but this may be a
consequence of that.

-- 
Dr Richard Stallman
Founder, Free Software Foundation (https://gnu.org, https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)

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

[Drew Adams]

> > 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.

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

[Stefan Kangas]

Drew Adams <drew.adams@oracle.com> writes:

> > > 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.

I don't see it in the subject line of the message you attached, but I
do see it in the original message I sent.

> 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.

I can see the headers just fine, here.

Best regards,
Stefan Kangas

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

[Drew Adams]

> > > 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.
> 
> I don't see it in the subject line of the message you attached, but I
> do see it in the original message I sent.

Thanks for checking.

Curiouser and curiouser.

> > 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.
> 
> I can see the headers just fine, here.

And curiouser.  (I guess you mean you can see them
in Outlook, as I described.  Or maybe you mean that
you can see them in another way?  In any case, you
confirm that they are present, even if I can't see
them.)

(I have Outlook 2016, FWIW.)

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

[Stephen Berman]

On Fri, 1 Nov 2019 15:23:07 -0700 (PDT) Drew Adams <drew.adams@oracle.com> wrote:

>> > > 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.
>>
>> I don't see it in the subject line of the message you attached, but I
>> do see it in the original message I sent.
>
> Thanks for checking.
>
> Curiouser and curiouser.
>
>> > 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.
>>
>> I can see the headers just fine, here.
>
> And curiouser.  (I guess you mean you can see them
> in Outlook, as I described.  Or maybe you mean that
> you can see them in another way?  In any case, you
> confirm that they are present, even if I can't see
> them.)
>
> (I have Outlook 2016, FWIW.)

As another datapoint, I also received an email from Stefan Kangas today
with no bug number in the subject line:

Subject: Re: 24.1.50; read-{buffer,file-name}-completion-ignore-case fails

But in the gmane.emacs.bugs newsgroup it shows up with the bug number:

Subject: bug#11339: 24.1.50;
 read-{buffer,file-name}-completion-ignore-case fails on non-ascii

Previous bug report emails from Stefan K I have received do have the bug
number.  I read both my email and newsgroups with Gnus.

Steve Berman

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

[Drew Adams]

> As another datapoint, I also received an email from Stefan Kangas today
> with no bug number in the subject line:
> 
> Subject: Re: 24.1.50; read-{buffer,file-name}-completion-ignore-case
> fails
> 
> But in the gmane.emacs.bugs newsgroup it shows up with the bug number:
> 
> Subject: bug#11339: 24.1.50;
>  read-{buffer,file-name}-completion-ignore-case fails on non-ascii
> 
> Previous bug report emails from Stefan K I have received do have the
> bug
> number.  I read both my email and newsgroups with Gnus.

Good to know.  Thanks.

Maybe something changed wrt debbugs recently?

I got mails from both Lars and Stefan K with
no bug # in the Subject today.  IOW, not just
one sender.

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

[Lars Ingebrigtsen]

Drew Adams <drew.adams@oracle.com> writes:

> Curiouser and curiouser.

I think it's due to me changing

https://debbugs.gnu.org/cgi/bugreport.cgi?bug=3000;mboxmaint=yes;mboxstat=yes

to 

https://debbugs.gnu.org/cgi/bugreport.cgi?mboxstat=yes;bug=3000

in gnus-bug-group-download-format-alist.  The former includes the bug
numbers in the subject, and the latter doesn't.  I think I'll change it
back again.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no

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

[Drew Adams]

> I think it's due to me changing ... to ...
> in gnus-bug-group-download-format-alist.  The former includes the bug
> numbers in the subject, and the latter doesn't.  I think I'll change it
> back again.

Cool.  Thanks for checking so promptly and trying that.

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

[Lars Ingebrigtsen]

Drew Adams <drew.adams@oracle.com> writes:

>> I think it's due to me changing ... to ...
>> in gnus-bug-group-download-format-alist.  The former includes the bug
>> numbers in the subject, and the latter doesn't.  I think I'll change it
>> back again.
>
> Cool.  Thanks for checking so promptly and trying that.

OK; changed back again now so the Subject lines should go back to the
way they were (with bug#) from now on in my emails.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no

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

[Eli Zaretskii]

> Date: Fri, 1 Nov 2019 14:34:59 -0700 (PDT)
> From: Drew Adams <drew.adams@oracle.com>
> Cc: larsi@gnus.org, 14659@debbugs.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.

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.

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

[Stefan Kangas]

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.

Best regards,
Stefan Kangas

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

[Eli Zaretskii]

> 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.