From: Eli Zaretskii <eliz@gnu.org>
To: "Gerd Möllmann" <gerd.moellmann@gmail.com>
Cc: 56808@debbugs.gnu.org
Subject: bug#56808: 29.0.50; Elusive display problem on macOS
Date: Thu, 28 Jul 2022 11:01:17 +0300 [thread overview]
Message-ID: <83czdpacoi.fsf@gnu.org> (raw)
In-Reply-To: <m2czdpzo0c.fsf@Mini.fritz.box> (message from Gerd Möllmann on Thu, 28 Jul 2022 09:37:23 +0200)
> From: Gerd Möllmann <gerd.moellmann@gmail.com>
> Cc: 56808@debbugs.gnu.org
> Date: Thu, 28 Jul 2022 09:37:23 +0200
>
> My current kind of working hypothesis is that this is caused by
> something in the "font department". When the problem is there, Emacs
> seems to behave completely consistently, assuming that it has the wrong
> value for the width of a space.
>
> For example, cursor movement in the wrongly displayed line, which should
> be using the current glyph row. The cursor movement is entirely okay,
> when a space were a bit wider than normal. From which I "conjecture"
> that the width of the space in the glyph row is already wrong.
If it's a font issue, "C-u C-x =" with the cursor on the space that is
larger than normal could help by showing the font used for that space.
> But then again, since the display of the run of spaces should be done as
> a string of characters in the same face, I also "conjecture" that the
> font of the face should be wrong. Which I find sort of strange.
> Shouldn't then all characters have the wrong size, and things would
> align again?
If Emacs decided, for some reason, to use a different font for some
character, it will generate a separate face for it, and that face is
not exposed to Lisp. (Normally, this only happens for non-ASCII
characters, though.) Btw, 'pgrow' shows the face ID as well, so it
can tell.
next prev parent reply other threads:[~2022-07-28 8:01 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 [this message]
2022-07-28 9:18 ` Gerd Möllmann
2022-07-28 11:31 ` Gerd Möllmann
2022-07-28 12:07 ` Gerd Möllmann
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83czdpacoi.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=56808@debbugs.gnu.org \
--cc=gerd.moellmann@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 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.