From: Wolfgang Jenkner <wjenkner@inode.at>
To: Eli Zaretskii <eliz@gnu.org>
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 21:43:31 +0200 [thread overview]
Message-ID: <85a96jazz0.fsf@iznogoud.viz> (raw)
In-Reply-To: <86f1a219-9ab5-439f-85ca-936b942cb034@default>
On Mon, Sep 01 2014, Eli Zaretskii wrote:
>> From: Wolfgang Jenkner <wjenkner@inode.at>
>> Date: Mon, 01 Sep 2014 20:45:58 +0200
>> Cc: 18367@debbugs.gnu.org
>>
>> On Sun, Aug 31 2014, Drew Adams wrote:
>>
>> > (elisp) `Other Font Lock Variables' says this about it:
>> >
>> > Variable: font-lock-extra-managed-props
>> > This variable specifies additional properties (other than
>> > `font-lock-face') that are being managed by Font Lock mode. It is
>> > used by `font-lock-default-unfontify-region', which normally only
>> > manages the `font-lock-face' property. If you want Font Lock to
>> > manage other properties as well, you must specify them in a
>> > FACESPEC in `font-lock-keywords' as well as add them to this list.
>> > *Note Search-based Fontification::.
>>
>> I think `font-lock-face' is a typo here (it should read `face').
>>
>> It is clear from looking a the code (or doing some experiments) that
>> font-lock-default-unfontify-region doesn't remove the `font-lock-face'
>> property.
>
> 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.
Sorry, for saying three times the same thing, but Drew cited this part
of the manual and it seems to be the reason why Stefan's request didn't
make sense to him.
Wolfgang
next prev parent reply other threads:[~2014-09-01 19:43 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 [this message]
2014-09-01 20:04 ` Eli Zaretskii
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=85a96jazz0.fsf@iznogoud.viz \
--to=wjenkner@inode.at \
--cc=18367@debbugs.gnu.org \
--cc=eliz@gnu.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 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).