From: Eli Zaretskii <eliz@gnu.org>
To: Milan Jovanovic <milanj@gmail.com>
Cc: 64101@debbugs.gnu.org, kklimonda@syntaxhighlighted.com,
joaotavora@gmail.com, monnier@iro.umontreal.ca
Subject: bug#64101: 29.0.91; Eglot inlay hints rendered out of order
Date: Tue, 20 Jun 2023 14:10:09 +0300 [thread overview]
Message-ID: <83edm675ke.fsf@gnu.org> (raw)
In-Reply-To: <410CA10A-75BB-4F88-B974-E69E349B3064@gmail.com> (message from Milan Jovanovic on Mon, 19 Jun 2023 23:05:49 +0200)
> From: Milan Jovanovic <milanj@gmail.com>
> Date: Mon, 19 Jun 2023 23:05:49 +0200
> Cc: Stefan Monnier <monnier@iro.umontreal.ca>,
> Eli Zaretskii <eliz@gnu.org>,
> Krzysztof Klimonda <kklimonda@syntaxhighlighted.com>,
> 64101@debbugs.gnu.org
>
> Looks like overlays render order depends on before-string/after-string property (beside priority).
Don't you expect that? If some text has both before-string and
after-string overlays, which one(s) will you expect to see before the
other one?
next prev parent reply other threads:[~2023-06-20 11:10 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
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 [this message]
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
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=83edm675ke.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=64101@debbugs.gnu.org \
--cc=joaotavora@gmail.com \
--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 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).