From: Eli Zaretskii <eliz@gnu.org>
To: Wolfgang Jenkner <wjenkner@inode.at>
Cc: 18367@debbugs.gnu.org
Subject: bug#18367: 24.4.50; [PATCH] Text property `font-lock-ignore', to protect from font-lock
Date: Mon, 01 Sep 2014 23:04:27 +0300 [thread overview]
Message-ID: <83r3zvf6pg.fsf@gnu.org> (raw)
In-Reply-To: <85a96jazz0.fsf@iznogoud.viz>
> From: Wolfgang Jenkner <wjenkner@inode.at>
> Cc: 18367@debbugs.gnu.org
> Date: Mon, 01 Sep 2014 21:43:31 +0200
>
> > The "it" in that text alludes to font-lock-extra-managed-props, not to
> > font-lock-face.
>
> I don't think the "it" is a problem here.
>
> > After all, the former is what is being documented in
> > the text you cited; the latter is just mentioned because
> > font-lock-face is another kind of specification of "additional"
> > properties of interest to Font Lock.
>
> But, `font-lock-face' is of no interest to
> font-lock-default-unfontify-region, the `face' property is.
>
> font-lock-default-unfontify-region does not remove the `font-lock-face'
> property, it removes the `face' property.
>
> font-lock-default-unfontify-region does not "manage" the
> `font-lock-face' property, it "manages" the `face' property.
The cited text says that font-lock-default-unfontify-region uses
font-lock-extra-managed-props. That is all it says; all the rest is
just comments and references to related features
.
next prev parent reply other threads:[~2014-09-01 20:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-30 20:12 bug#18367: 24.4.50; [PATCH] Text property `font-lock-ignore', to protect from font-lock Drew Adams
2014-08-31 12:47 ` Stefan Monnier
2014-08-31 15:30 ` Drew Adams
2014-08-31 20:08 ` Stefan Monnier
2014-08-31 20:56 ` Drew Adams
2014-09-01 18:45 ` Wolfgang Jenkner
2014-09-01 19:08 ` Eli Zaretskii
2014-09-01 19:43 ` Wolfgang Jenkner
2014-09-01 20:04 ` Eli Zaretskii [this message]
2014-09-30 16:45 ` Michael Heerdegen
2014-09-30 17:14 ` Drew Adams
2015-06-20 16:58 ` Drew Adams
2016-04-30 13:44 ` Lars Ingebrigtsen
2016-04-30 16:32 ` Drew Adams
2016-04-30 14:28 ` Stefan Monnier
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=83r3zvf6pg.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=18367@debbugs.gnu.org \
--cc=wjenkner@inode.at \
/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).