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 19:13:17 +0200 [thread overview]
Message-ID: <m2tu71xis2.fsf@Mini.fritz.box> (raw)
In-Reply-To: <83r1258e4q.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 28 Jul 2022 18:12:53 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
> It shouldn't, but why do you need LSP? xref-find-references has local
> alternatives for that, e.g. ID-Utils or Grep.
Good idea.
>
>> 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?
That's the 42€ question.
BTW, as I meanwhile realize, max-width is also set to 8. Max-width is
computed a few lines below space-width. From reading the code, I'd say
that is most likely when space-width has already been 8 there. Which
leaves only a small window for overwriting.
Or both have been overwritten. Many things are possible. ATM, it's
just my gut telling me it's not overwritten.
next prev parent reply other threads:[~2022-07-28 17:13 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
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 [this message]
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=m2tu71xis2.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).