all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: "João Távora" <joaotavora@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>,
	Krzysztof Klimonda <kklimonda@syntaxhighlighted.com>,
	64101@debbugs.gnu.org
Subject: bug#64101: 29.0.91; Eglot inlay hints rendered out of order
Date: Sun, 18 Jun 2023 10:36:13 -0400	[thread overview]
Message-ID: <jwvsfaozvs0.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87mt0w7sv2.fsf@gmail.com> ("João Távora"'s message of "Sun, 18 Jun 2023 15:22:25 +0100")

>    ;; This buffer is for text that is not saved, and for Lisp evaluation.
>    ;; To create a file, visit it with C-x C-f and enter text in its buffer.
>     
>    (progn
>      (mapc #'delete-overlay (overlays-in (point-min) (point-max)))
>      (let ((a (make-overlay 10 20))
>            (b (make-overlay 10 20)))
>        (overlay-put a 'after-string (propertize "aaaa" 'face 'highlight))
>        (overlay-put b 'after-string (propertize "bbbb" 'face 'speedbar-highlight-face))
>        ;; (overlay-put a 'priority 1)
>        ;; (overlay-put b 'priority 2)
>        (overlay-put a 'priority `(nil . 1))
>        (overlay-put b 'priority `(nil . 2))
>        ))
>
> This displays AAAABBBB eventually, but I would expect it to show
> BBBBAAAA, which is what I get if I use "primary" priorities.

Hmm... I see that the (PRIMARY . SECONDARY) priority format is only
understood by `make_sortvec_item`, but not by
xdisp.c:RECORD_OVERLAY_STRING nor by buffer.c:record_overlay_string.

> Anyway, can you explain this?

[ Revised answer: ]  Yes.


        Stefan






  parent reply	other threads:[~2023-06-18 14:36 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 [this message]
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
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=jwvsfaozvs0.fsf-monnier+emacs@gnu.org \
    --to=bug-gnu-emacs@gnu.org \
    --cc=64101@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=joaotavora@gmail.com \
    --cc=kklimonda@syntaxhighlighted.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.