From: "Gerd Möllmann" <gerd.moellmann@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 56808@debbugs.gnu.org
Subject: bug#56808: 29.0.50; Elusive display problem on macOS
Date: Thu, 28 Jul 2022 14:07:09 +0200 [thread overview]
Message-ID: <m235elzbiq.fsf@Mini.fritz.box> (raw)
In-Reply-To: <m25yjhzd6t.fsf@Mini.fritz.box> ("Gerd Möllmann"'s message of "Thu, 28 Jul 2022 13:31:06 +0200")
Gerd Möllmann <gerd.moellmann@gmail.com> writes:
> This is the font of the default face in both cases...
And space-width seems to come from nsfont.m:2696, which I found with
LSP/find references:
glyph = macfont_get_glyph_for_character (font, ' ');
if (glyph != kCGFontIndexInvalid)
font->space_width = macfont_glyph_extents (font, glyph, NULL, NULL, 0);
else
/* dirty workaround */
font->space_width = pixel_size;
I don't think the else branch has been taken, because that wouldn't lead
to a value of 8.
Suspiciously, the last argument of macfont_glyph_extents is 0 (false),
and the parameter is named force_integral_p. Hm, space_width is an
integer?
But, I'm afraid I'm out here. I don't understand these functions at
all.
BTW, a clear-font-cache didn't help, and yes, I don't know what it does
:-).
next prev parent reply other threads:[~2022-07-28 12:07 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-28 5:09 bug#56808: 29.0.50; Elusive display problem on macOS Gerd Möllmann
2022-07-28 6:04 ` Eli Zaretskii
2022-07-28 7:37 ` Gerd Möllmann
2022-07-28 8:01 ` Eli Zaretskii
2022-07-28 9:18 ` Gerd Möllmann
2022-07-28 11:31 ` Gerd Möllmann
2022-07-28 12:07 ` Gerd Möllmann [this message]
2022-07-28 13:03 ` Gerd Möllmann
2022-07-28 13:37 ` Eli Zaretskii
2022-07-28 15:04 ` Gerd Möllmann
2022-07-28 15:12 ` Eli Zaretskii
2022-07-28 17:13 ` Gerd Möllmann
2022-07-29 12:32 ` Gerd Möllmann
2022-07-29 13:52 ` YAMAMOTO Mitsuharu
2022-07-29 14:32 ` Gerd Möllmann
2022-07-30 7:49 ` YAMAMOTO Mitsuharu
2022-07-30 7:54 ` Gerd Möllmann
2022-07-30 8:13 ` Eli Zaretskii
2022-07-30 8:28 ` YAMAMOTO Mitsuharu
2022-07-29 13:17 ` Alexander Adolf
2022-07-29 14:18 ` Gerd Möllmann
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=m235elzbiq.fsf@Mini.fritz.box \
--to=gerd.moellmann@gmail.com \
--cc=56808@debbugs.gnu.org \
--cc=eliz@gnu.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).