From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: lockywolf@gmail.com, schwab@linux-m68k.org, 35816@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 15:48:28 +0300 [thread overview]
Message-ID: <83v94ade1v.fsf@gnu.org> (raw)
In-Reply-To: <87pmuin8ze.fsf@gnus.org> (message from Lars Ingebrigtsen on Thu, 12 Aug 2021 14:27:49 +0200)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: schwab@linux-m68k.org, lockywolf@gmail.com, 35816@debbugs.gnu.org
> Date: Thu, 12 Aug 2021 14:27:49 +0200
>
> Eli Zaretskii <eliz@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.
AFAIR, we eventually convert all the other forms into XLFD format.
> > 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?
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".
> > 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.
Thanks!
next prev parent reply other threads:[~2021-08-12 12:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-21 1:56 bug#35816: 26.2; set-frame-font cannot set some fonts which autocomplete suggests due to dashes in names. I.e. gnu-unifont Vladimir Nikishkin
2019-07-09 2:20 ` Lars Ingebrigtsen
[not found] ` <CA+A2iZY8bT-prYgB6oTrv6oY4Kyicpo4o52A3jAVVL7yLtjEhg@mail.gmail.com>
2019-07-09 13:22 ` Lars Ingebrigtsen
2019-07-09 13:55 ` Vladimir Nikishkin
2021-08-11 19:02 ` Lars Ingebrigtsen
2021-08-11 19:27 ` Andreas Schwab
2021-08-11 19:33 ` Lars Ingebrigtsen
2021-08-11 20:04 ` Lars Ingebrigtsen
2021-08-12 6:56 ` Eli Zaretskii
2021-08-12 7:31 ` Andreas Schwab
2021-08-12 8:10 ` Eli Zaretskii
2021-08-12 12:30 ` Lars Ingebrigtsen
2021-08-12 12:27 ` Lars Ingebrigtsen
2021-08-12 12:48 ` Eli Zaretskii [this message]
2021-08-12 12:53 ` Lars Ingebrigtsen
2021-08-12 13:06 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83v94ade1v.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=35816@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=lockywolf@gmail.com \
--cc=schwab@linux-m68k.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.