GNU bug report logs - #56808
29.0.50; Elusive display problem on macOS

Previous Next

Package: emacs;

Reported by: Gerd Möllmann <gerd.moellmann <at> gmail.com>

Date: Thu, 28 Jul 2022 05:10:02 UTC

Severity: normal

Found in version 29.0.50

Done: YAMAMOTO Mitsuharu <mituharu <at> math.s.chiba-u.ac.jp>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Gerd Möllmann <gerd.moellmann <at> gmail.com>
Cc: 56808 <at> debbugs.gnu.org
Subject: bug#56808: 29.0.50; Elusive display problem on macOS
Date: Thu, 28 Jul 2022 18:12:53 +0300
> From: Gerd Möllmann <gerd.moellmann <at> gmail.com>
> Cc: 56808 <at> debbugs.gnu.org
> Date: Thu, 28 Jul 2022 17:04:59 +0200
> 
> Eli Zaretskii <eliz <at> gnu.org> writes:
> 
> > M-? (a.k.a. xref-find-references) cannot find it?
> 
> No it doesn't.  Apparently it doesn't use the lsp backend.  Don't know
> if it should.

It shouldn't, but why do you need LSP?  xref-find-references has local
alternatives for that, e.g. ID-Utils or Grep.

> >>   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.
> >
> > Maybe you should run with a watchpoint on font->space_width.
> 
> I suspect that it's really 8 at some point during startup, and that it
> isn't overwritten.  The reason for this is that the two places above are
> the only ones assigning to space_width, which I trust clangd to know.

Then how did you get 7 in the other image you posted?




This bug report was last modified 3 years and 10 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.