From: "João Távora" <joaotavora@gmail.com>
To: Milan Jovanovic <milanj@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>,
Krzysztof Klimonda <kklimonda@syntaxhighlighted.com>,
Stefan Monnier <monnier@iro.umontreal.ca>,
64101@debbugs.gnu.org
Subject: bug#64101: 29.0.91; Eglot inlay hints rendered out of order
Date: Mon, 19 Jun 2023 17:34:07 +0100 [thread overview]
Message-ID: <CALDnm53RwHY41dUVejkb7Jjs4EEaHLidmY458TpvoNAZNJLXMA@mail.gmail.com> (raw)
In-Reply-To: <860E88E5-F4B5-4DEB-B64B-D201AB811E02@gmail.com>
On Mon, Jun 19, 2023 at 5:17 PM Milan Jovanovic <milanj@gmail.com> wrote:
>
> João, is there a reason why (in Eglot) hint parts can’t be merged and only one overlay created ?
Yes, in general you want to keep different properties of different
labels, such as URL links isolated.
> I fix it to create one overlay and I haven’t noticed any issues (I use it only with the rust-analyzer though).
> Don’t know if this is stupid question, don’t know much about LSP protocol (or Emacs internals).
It's not a stupid question at all, and it's a possibility, but
I have to understand the problem first, and if you haven't
yet understood that, I don't have a Mac OS machine to test.
Before trying fixes, or at least while you're trying them,
please I urge you to provide a reproduction recipe for whatever
you're trying to do. Your last follow-up bug report is completely strange
to me: in the situation you last described there aren't any
multiple coinciding overlays like in the original report of Krzysztof.
João
next prev parent reply other threads:[~2023-06-19 16:34 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-15 21:23 bug#64101: 29.0.91; Eglot inlay hints rendered out of order Krzysztof Klimonda
2023-06-17 7:56 ` Eli Zaretskii
2023-06-17 9:39 ` João Távora
2023-06-17 10:41 ` Eli Zaretskii
2023-06-17 12:19 ` João Távora
2023-06-17 13:17 ` Eli Zaretskii
2023-06-17 13:26 ` João Távora
2023-06-17 14:12 ` Eli Zaretskii
2023-06-17 14:29 ` João Távora
2023-06-17 15:50 ` Eli Zaretskii
2023-06-17 16:45 ` João Távora
2023-06-17 12:26 ` Krzysztof Klimonda
2023-06-17 19:02 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-17 22:25 ` João Távora
2023-06-18 0:45 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-18 8:47 ` João Távora
2023-06-18 14:18 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-18 14:22 ` João Távora
2023-06-18 14:29 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-18 14:36 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-18 15:20 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-19 16:17 ` Milan Jovanovic
2023-06-19 16:34 ` João Távora [this message]
2023-06-19 18:06 ` Milan Jovanovic
2023-06-19 19:08 ` João Távora
2023-06-19 21:05 ` Milan Jovanovic
2023-06-19 22:38 ` João Távora
2023-06-20 11:10 ` Eli Zaretskii
2023-06-20 11:32 ` Milan Jovanovic
2023-06-20 12:01 ` Eli Zaretskii
2023-06-20 13:34 ` Milan Jovanovic
2023-06-20 13:46 ` Eli Zaretskii
2023-06-20 13:50 ` João Távora
2023-06-17 20:54 ` Milan Jovanovic
2023-06-17 22:35 ` 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=CALDnm53RwHY41dUVejkb7Jjs4EEaHLidmY458TpvoNAZNJLXMA@mail.gmail.com \
--to=joaotavora@gmail.com \
--cc=64101@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=kklimonda@syntaxhighlighted.com \
--cc=milanj@gmail.com \
--cc=monnier@iro.umontreal.ca \
/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.