From: Mohsin Kaleem <mohkale@kisara.moe>
To: "João Távora" <joaotavora@gmail.com>, "Eli Zaretskii" <eliz@gnu.org>
Cc: 71282@debbugs.gnu.org, stefankangas@gmail.com
Subject: bug#71282: 30.0.50; hl-line overlay priority has no affect
Date: Sun, 30 Jun 2024 16:21:05 +0100 [thread overview]
Message-ID: <87zfr2bgny.fsf@kisara.moe> (raw)
In-Reply-To: <CALDnm52ON7V55Z8GzOR4QB1WiZPq+EtiW=u_PA0_D+T0oNd7BA@mail.gmail.com>
João Távora <joaotavora@gmail.com> writes:
> This mechanism shouldn't rely on making X aware of Y. Maybe if the
> implementation of Y were moved to C display core, like
> display-line-numbers-mode. Or maybe not, I haven't looked into it (and
> I don't plan to, sorry).
Thanks João.
Going to back to the original discussion is there a reason
before-strings in overlays don't respect priorities? I realise it's
documented but I'm more curious about the why than the what? Was there a
use case for these properties in overlays to not be overridable (which
from what I understand is the reason for this conflict between hl-line and
overlay annotations is happening).
--
Mohsin Kaleem
next prev parent reply other threads:[~2024-06-30 15:21 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
2024-06-30 15:12 ` João Távora
2024-06-30 15:21 ` Mohsin Kaleem [this message]
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
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=87zfr2bgny.fsf@kisara.moe \
--to=mohkale@kisara.moe \
--cc=71282@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=joaotavora@gmail.com \
--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 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).