From: "João Távora" <joaotavora@gmail.com>
To: Mohsin Kaleem <mohkale@kisara.moe>
Cc: Eli Zaretskii <eliz@gnu.org>,
71282@debbugs.gnu.org, stefankangas@gmail.com
Subject: bug#71282: 30.0.50; hl-line overlay priority has no affect
Date: Mon, 1 Jul 2024 14:50:59 +0100 [thread overview]
Message-ID: <CALDnm53WhDEVZMB6R4Ww4ykAse-uZJ3EsH+_svAuk3b0-biMmA@mail.gmail.com> (raw)
In-Reply-To: <87tth9uw5z.fsf@kisara.moe>
On Mon, Jul 1, 2024 at 1:35 PM Mohsin Kaleem <mohkale@kisara.moe> wrote:
>
> Eli Zaretskii <eliz@gnu.org> writes:
> >>
> >> Then if that mechanism doesn't require anything specific of package X or
> >> Y, it should be possible to condense in a function (that shouldn't live in
> >> Eglot, but OK it it starts life there, I guess) that takes a face with
> >> a number of
> >> attributes,merges with whatever is "the face of the buffer text" and return
> >> an (anonymous) face. If so, then that "mistery" function is the fix
> >> to this issue.
> >
> > Patches welcome.
>
> Any tips or suggestions for where to start if one wants to implement
> something like this? I'll try taking a look at some of the related code
> and how to get some kind of merging setup. Probably not very soon tho
> XD.
Moshin, I don't know if you read my later email, but I'd like to point
out that that function, which I briefly thought could be used to fix this
issue, is NOT the solution. I'm fairly sure it won't work, at least
not for the hl-line use case you bring forth. As far as I can see,
short of an xdisp.c fix for this, the Elisp solution is very hard and
involves hl-line doing perhaps extraordinary amounts of work in
'hl-line-highlight' and 'hl-line-unhighlight' to account for intersecting
overlays, their after strings, before strings, but only in those
parts that touch the line to be highlighted.
João
next prev parent reply other threads:[~2024-07-01 13:50 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
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 [this message]
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=CALDnm53WhDEVZMB6R4Ww4ykAse-uZJ3EsH+_svAuk3b0-biMmA@mail.gmail.com \
--to=joaotavora@gmail.com \
--cc=71282@debbugs.gnu.org \
--cc=eliz@gnu.org \
--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 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).