GNU bug report logs - #35816
26.2; set-frame-font cannot set some fonts which autocomplete suggests due to dashes in names. I.e. gnu-unifont

Previous Next

Full log

View this message in rfc822 format

From: Lars Ingebrigtsen <larsi <at> gnus.org>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: lockywolf <at> gmail.com, schwab <at> linux-m68k.org, 35816 <at> debbugs.gnu.org
Subject: bug#35816: 26.2; set-frame-font cannot set some fonts which autocomplete suggests due to dashes in names. I.e. gnu-unifont
Date: Thu, 12 Aug 2021 14:53:30 +0200

Eli Zaretskii <eliz <at> gnu.org> writes:

>> This bug was only about XLFD fonts, though.
>
> AFAIR, we eventually convert all the other forms into XLFD format.

Oh, we do?  I didn't know that.  Well, then there might be problems.
But...  why?  I thought everything got parsed into font-spec structures.

>> I didn't see anything about dashes in the set-face-font doc string?
>
>   The format of the font string specification varies based on the font
>   system in use, but it can commonly be an X Logical Font
>   Description (XLFD) string, or a simpler string like "Courier-10"
>   or "courier:size=10".

Right.  

(font-spec :name "Courier-10")
=> #<font-spec nil nil Courier nil nil nil nil nil 10.0 nil nil nil ((:name . "Courier-10"))>

(font-spec :name "Courier-Foo-10")
=> #<font-spec nil nil Courier-Foo nil nil nil nil nil 10.0 nil nil nil ((:name . "Courier-Foo-10"))>

Both before and after the changes.

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

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.