From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: luangruo@yahoo.com, 57962@debbugs.gnu.org, stefankangas@gmail.com
Subject: bug#57962: 29.0.50; Odd font choices
Date: Mon, 17 Oct 2022 17:26:43 +0300 [thread overview]
Message-ID: <83wn8y1q70.fsf@gnu.org> (raw)
In-Reply-To: <87czaqel7x.fsf@gnus.org> (message from Lars Ingebrigtsen on Mon, 17 Oct 2022 13:35:46 +0200)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: luangruo@yahoo.com, 57962@debbugs.gnu.org, stefankangas@gmail.com
> Date: Mon, 17 Oct 2022 13:35:46 +0200
>
> > Is that because ":spacing 'm" doesn't work (it seems to work for me)?
> > If so, I think we should try fixing that instead of introducing new
> > wizardry.
>
> This:
>
> (defface fixed-pitch
> `((t :font ,(font-spec :spacing 'M)))
> "The basic fixed-pitch face."
> :group 'basic-faces)
>
> Made Emacs choose this font:
>
> ftcrhb:-GOOG-Noto Sans CJK KR-regular-normal-normal-*-45-*-*-*-*-0-iso10646-1 (#x24)
>
> Which is not a monospace font (and is a different font family than the
> `default' face uses:
>
> ftcrhb:-DAMA-Ubuntu Mono-regular-normal-normal-*-45-*-*-*-m-0-iso10646-1 (#x47)
>
> So that seems to be another bug in this area?
Maybe this is because font_delete_unmatched doesn't pay attention to
:spacing? Can you try adding that there, to see whether it could fix
this?
font_sort_entities and font_match_p also could be related, but I don't
know if they are called in this scenario.
next prev parent reply other threads:[~2022-10-17 14:26 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-20 22:16 bug#57962: 29.0.50; Odd font choices Lars Ingebrigtsen
2022-09-21 2:19 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-21 10:43 ` Lars Ingebrigtsen
2022-10-14 11:41 ` Lars Ingebrigtsen
2022-10-14 11:53 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-14 12:02 ` Lars Ingebrigtsen
2022-10-14 12:05 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-14 12:13 ` Lars Ingebrigtsen
2022-10-14 12:20 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-14 12:07 ` Eli Zaretskii
2022-10-14 12:18 ` Lars Ingebrigtsen
2022-10-14 12:37 ` Eli Zaretskii
2022-10-14 12:48 ` Lars Ingebrigtsen
2022-10-14 13:00 ` Eli Zaretskii
2022-10-14 13:06 ` Lars Ingebrigtsen
2022-10-14 13:09 ` Eli Zaretskii
2022-10-16 10:58 ` Lars Ingebrigtsen
2022-10-16 11:17 ` Eli Zaretskii
2022-10-16 12:19 ` Lars Ingebrigtsen
2022-10-16 13:53 ` Eli Zaretskii
2022-10-17 9:57 ` Lars Ingebrigtsen
2022-10-17 10:22 ` Eli Zaretskii
2022-10-17 11:35 ` Lars Ingebrigtsen
2022-10-17 12:58 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-17 14:26 ` Eli Zaretskii [this message]
2022-10-17 14:20 ` Stefan Kangas
2022-10-17 14:34 ` Eli Zaretskii
2022-10-17 15:40 ` Stefan Kangas
2022-10-18 0:38 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=83wn8y1q70.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=57962@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=luangruo@yahoo.com \
--cc=stefankangas@gmail.com \
/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).