From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: luangruo@yahoo.com, 57962@debbugs.gnu.org
Subject: bug#57962: 29.0.50; Odd font choices
Date: Sun, 16 Oct 2022 14:19:03 +0200 [thread overview]
Message-ID: <87v8okhsg8.fsf@gnus.org> (raw)
In-Reply-To: <83tu443tlo.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 16 Oct 2022 14:17:55 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
> When we select a suitable font, we generally avoid opening a font,
> because that's expensive. So looking at the metrics is not possible,
> unless we actually open each font.
Right... but after opening a font, we could determine that it was
unsuitable at that point, and then choose another. That way the happy
path would still be fast.
> But I don't think I understand what is going on here: these two fonts
> are of the same size -- 48 -- so how come the glyphs have different
> sizes? And how different are they? Can you look at the character
> metrics inside gui_produce_glyphs and tell what we get from each font?
I haven't, but if I emacs -geometry 80x10 -fn "DejaVu Sans Mono-15" -Q,
I get an Emacs frame that is 2508x762 pixels. With -fn "Ubuntu Mono-15"
I get a frame that's 2128x662 pixels, so DejaVu Sans Mono is about 18%
larger than Ubuntu Mono, which is noticeable, and makes mixing the two
fonts non-ideal.
next prev parent reply other threads:[~2022-10-16 12:19 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87v8okhsg8.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=57962@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=luangruo@yahoo.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 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.