From: Juri Linkov <juri@jurta.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 14645@debbugs.gnu.org
Subject: bug#14645: Keep highlighting face foreground
Date: Fri, 14 Aug 2020 02:44:43 +0300 [thread overview]
Message-ID: <87pn7um4sw.fsf@mail.linkov.net> (raw)
In-Reply-To: <87r1sadbn6.fsf@gnus.org> (Lars Ingebrigtsen's message of "Thu, 13 Aug 2020 13:32:29 +0200")
>> Another place where `add-face-text-property' could help is for the
>> recently added face `info-index-match'. Currently it looks very ugly
>> when the `info-index-match' face is added in the middle of a link
>> that breaks its continuity. A test case is: `C-h r I match RET'.
>>
>> This is because `Info-index' adds the `info-index-match' face to the
>> strings of the found index entries. Later `Info-virtual-index-find-node'
>> inserts strings to the Info buffer. And finally `Info-fontify-node'
>> puts the `font-lock-face' property with `info-xref' on links.
>> The `face info-index-match' takes precedence over `font-lock-face info-xref'.
>
> This hadn't been fixed, so I applied your patch to Emacs 28.
This patch breaks Info fontification, please revert it.
Here is what I said in the message sent later with another patch at
https://debbugs.gnu.org/14645#14
Using the text property `face' instead of `font-lock-face'
might break something, so a better patch below removes
the text properties `face info-index-match' from the Info buffer
This is why I posted a better patch. But please give me more time
to test the second better patch, I'm not yet sure how well it works now.
next prev parent reply other threads:[~2020-08-13 23:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-17 22:55 bug#14645: Keep highlighting face foreground Juri Linkov
2013-06-18 23:31 ` Juri Linkov
2013-06-19 23:14 ` Juri Linkov
2020-08-13 11:35 ` Lars Ingebrigtsen
2013-06-20 23:03 ` Juri Linkov
2020-08-13 11:32 ` Lars Ingebrigtsen
2020-08-13 23:44 ` Juri Linkov [this message]
2020-08-14 6:20 ` Eli Zaretskii
2020-08-14 9:50 ` Lars Ingebrigtsen
2020-08-13 11:27 ` Lars Ingebrigtsen
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=87pn7um4sw.fsf@mail.linkov.net \
--to=juri@jurta.org \
--cc=14645@debbugs.gnu.org \
--cc=larsi@gnus.org \
/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.