From: Lars Ingebrigtsen <larsi@gnus.org>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: Vladimir Nikishkin <lockywolf@gmail.com>, 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: Wed, 11 Aug 2021 22:04:37 +0200 [thread overview]
Message-ID: <877dgrpx2i.fsf@gnus.org> (raw)
In-Reply-To: <87bl63pyi8.fsf@gnus.org> (Lars Ingebrigtsen's message of "Wed, 11 Aug 2021 21:33:35 +0200")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> Thanks! After an "apt install fonts-mikachan" I can now reproduce the
> problem on this Debian/bullseye system, too, and I'll try to see whether
> I can come up with a solution.
And I've now made font_parse_xlfd try harder to make sense of font names
like:
(set-frame-font "-Take-mikachan-puchi-normal-normal-normal-*-*-*-*-*-*-0-iso10646-1")
I've tried to be as backwards-compatible as possible -- only trying to
interpret this as a family name of "mikachan-puchi" is parsing it the
normal way fails.
So this should be fixed in Emacs 28.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2021-08-11 20:04 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 [this message]
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
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
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=877dgrpx2i.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=35816@debbugs.gnu.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 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).