From: Eli Zaretskii <eliz@gnu.org>
To: Chinmay Dalal <dalal.chinmay.0101@gmail.com>
Cc: 61812@debbugs.gnu.org
Subject: bug#61812: 30.0.50; Eglot inlay hints "pile up"
Date: Sun, 26 Feb 2023 16:35:52 +0200 [thread overview]
Message-ID: <83sfesijef.fsf@gnu.org> (raw)
In-Reply-To: <ypi9o7pgv8hn.fsf@gmail.com> (message from Chinmay Dalal on Sun, 26 Feb 2023 19:20:04 +0530)
> From: Chinmay Dalal <dalal.chinmay.0101@gmail.com>
> Cc: 61812@debbugs.gnu.org
> Date: Sun, 26 Feb 2023 19:20:04 +0530
>
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> From: Chinmay Dalal <dalal.chinmay.0101@gmail.com>
> >> Cc: 61812@debbugs.gnu.org
> >> Date: Sun, 26 Feb 2023 18:29:35 +0530
> >>
> >> > And if the latter, what exactly
> >> > causes the duplicates? You say "scroll around", but how do you
> >> > "scroll around" (with what commands), and can you try figuring out
> >> > what exactly triggers the appearance of the duplicates?
> >>
> >> "Scroll around" was inaccurate, apologies. I meant using C-n/C-p to move
> >> the cursor.
> >
> > So if you move through a region with C-n/C-p time and again, you will
> > see the duplicates appear one by one?
>
> Yes, this is not deterministic though - some places have duplicates,
> some don't
>
> > If you go to the place where the duplicate hints are shown and type
> > "M-x describe-text-properties RET", how many overlays are shown in the
> > window Emacs pops up? Do you see a separate overlay for each
> > duplication?
>
> Yes, there are separate overlays for each duplication, for example:
>
> From 7070 to 7070
> before-string [Show]
> eglot--inlay-hint t
> eglot--overlay t
> From 7070 to 7070
> before-string [Show]
> eglot--inlay-hint t
> eglot--overlay t
So it sounds like we are not deleting old overlays before adding new
ones.
Or maybe we should delete them automatically when point moves far
enough?
next prev parent reply other threads:[~2023-02-26 14:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-26 12:24 bug#61812: 30.0.50; Eglot inlay hints "pile up" Chinmay Dalal
2023-02-26 12:35 ` Eli Zaretskii
2023-02-26 12:59 ` Chinmay Dalal
2023-02-26 13:15 ` Eli Zaretskii
2023-02-26 13:50 ` Chinmay Dalal
2023-02-26 14:35 ` Eli Zaretskii [this message]
2023-02-27 13:06 ` Chinmay Dalal
2023-02-27 14:05 ` João Távora
2023-02-27 14:33 ` João Távora
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=83sfesijef.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=61812@debbugs.gnu.org \
--cc=dalal.chinmay.0101@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.