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

Message #40 received at 35816 <at> debbugs.gnu.org (full text, mbox):

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: Re: 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:27:49 +0200

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

> set-frame-font is not the only API that accepts font names, and XLFD
> is not the only format of fonts Emacs accepts

This bug was only about XLFD fonts, though.

> Do the changes you made affect that code in any way

Nope.

> Also, perhaps set-face-font can now accept font names that
> include a dash which not only precedes a numeric size, in which case
> at least the doc string of set-face-font should be amended?

I didn't see anything about dashes in the set-face-font doc string?

> Finally, I think it would be good to have some tests for these issues,
> as much as possible (we cannot set fonts in batch mode, but perhaps
> using lower-level APIs that parse the font spec would allow such
> tests).

I didn't find any Lisp-level interfaces that exposed this yesterday, but
I now see that `(font-spec :name ...)' was what I was looking for, so
I've added a couple of tests.

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