From: Eli Zaretskii <eliz@gnu.org>
To: Vasilij Schneidermann <mail@vasilij.de>
Cc: 42138@debbugs.gnu.org
Subject: bug#42138: 26.3; Incompatibility between font-lock-add-keywords and enriched.el
Date: Mon, 20 Jul 2020 17:40:16 +0300 [thread overview]
Message-ID: <83o8oagshb.fsf@gnu.org> (raw)
In-Reply-To: <20200720065931.GA5179@odonien.localdomain> (message from Vasilij Schneidermann on Mon, 20 Jul 2020 08:59:31 +0200)
> Date: Mon, 20 Jul 2020 08:59:31 +0200
> From: Vasilij Schneidermann <mail@vasilij.de>
> Cc: 42138@debbugs.gnu.org
>
> > I think enriched-mode, like any other mode that puts its own faces on
> > chunks of text by means other than font-lock, is fundamentally
> > incompatible with font-lock. It's basically the same problem as if
> > you tried to use put-text-property in *scratch* to put some face
> > property on some text in the buffer: the face won't show until you
> > turn off font-lock. That's because the first thing font-lock does is
> > wipe out all the faces in the buffer.
>
> Thanks for the clarification. This doesn't really help me though, I want to
> adjust my existing font-lock using code so that it detects when it would wipe
> out said text properties enriched-mode set up. It doesn't appear to be
> sufficient to just check whether `font-lock-mode` is non-nil, if I do that
> inside the example enriched.txt file, it's set to `t` for some reason. Again,
> what would the correct check be here?
I think you want to look at font-lock-defaults.
> > Any way that uses put-text-property, add-text-properties, etc. without
> > using font-lock will do. You can even try that manually via the
> > facemenu-set-* commands (or via the Edit->Text Properties menu from
> > the menu bar).
>
> Hm, I've done that for non-font-lock scenarios before, but in this case I
> really need font-lock's ability to search for strings and apply fontification
> to them, so this isn't really an option. Looking for other examples in the
> Emacs sources I've found uses of `jit-lock-register`.
Ah, I guess I misunderstood what kind of solutions you are looking
for, sorry.
If you want to keep font-lock in effect, then indeed jit-lock-register
is one feature to look at. But there are two others:
font-lock-extra-managed-props and the font-lock-face property. I hope
one of these will allow you to come up with a solution.
next prev parent reply other threads:[~2020-07-20 14:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-30 13:08 bug#42138: 26.3; Incompatibility between font-lock-add-keywords and enriched.el Vasilij Schneidermann
2020-06-30 16:32 ` Eli Zaretskii
2020-07-20 6:59 ` Vasilij Schneidermann
2020-07-20 14:40 ` Eli Zaretskii [this message]
2020-07-25 21:37 ` Vasilij Schneidermann
2020-07-26 2:31 ` 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=83o8oagshb.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=42138@debbugs.gnu.org \
--cc=mail@vasilij.de \
/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).