From: Eli Zaretskii <eliz@gnu.org>
To: Mohsin Kaleem <mohkale@kisara.moe>
Cc: 71282@debbugs.gnu.org, joaotavora@gmail.com, stefankangas@gmail.com
Subject: bug#71282: 30.0.50; hl-line overlay priority has no affect
Date: Sun, 30 Jun 2024 17:46:53 +0300 [thread overview]
Message-ID: <867ce6h4iq.fsf@gnu.org> (raw)
In-Reply-To: <875xtqczuu.fsf@kisara.moe> (message from Mohsin Kaleem on Sun, 30 Jun 2024 14:41:13 +0100)
> From: Mohsin Kaleem <mohkale@kisara.moe>
> Cc: stefankangas@gmail.com, 71282@debbugs.gnu.org
> Date: Sun, 30 Jun 2024 14:41:13 +0100
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > The only way I can think of is for Eglot to be sensitive to hl-line
> > and to set up the colors of the inlay hints to be consistent with the
> > hl-line's background. Not sure if João (CC'ed) will like this.
> >
> > FWIW, I see no problem in the current behavior, but then I'm not an
> > hl-line user.
>
> This seems at least to me like a problem not specific to eglot. Any
> package trying to support overlay annotations in buffer will have the
> same problem.
I don't think it's a "problem". Overlay strings have their own faces,
and those override the faces of buffer text.
next prev parent reply other threads:[~2024-06-30 14:46 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-30 22:27 bug#71282: 30.0.50; hl-line overlay priority has no affect Mohsin Kaleem
2024-05-31 5:44 ` Eli Zaretskii
2024-06-30 6:10 ` Stefan Kangas
2024-06-30 11:42 ` Mohsin Kaleem
2024-06-30 12:23 ` Eli Zaretskii
2024-06-30 13:41 ` Mohsin Kaleem
2024-06-30 14:46 ` Eli Zaretskii [this message]
2024-06-30 15:12 ` João Távora
2024-06-30 15:21 ` Mohsin Kaleem
2024-06-30 15:37 ` Eli Zaretskii
2024-06-30 15:34 ` Eli Zaretskii
2024-06-30 15:50 ` João Távora
2024-06-30 16:37 ` João Távora
2024-06-30 17:36 ` Eli Zaretskii
2024-06-30 18:09 ` João Távora
2024-07-01 12:35 ` Mohsin Kaleem
2024-07-01 13:50 ` João Távora
2024-06-30 15:18 ` Mohsin Kaleem
2024-06-30 17:28 ` Eli Zaretskii
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=867ce6h4iq.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=71282@debbugs.gnu.org \
--cc=joaotavora@gmail.com \
--cc=mohkale@kisara.moe \
--cc=stefankangas@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.