From: Wolfgang Jenkner <wjenkner@inode.at>
To: Drew Adams <drew.adams@oracle.com>
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 20:45:58 +0200 [thread overview]
Message-ID: <85mwajb2mx.fsf@iznogoud.viz> (raw)
In-Reply-To: <de164f82-1fee-4145-be5c-882daa95a876@default> (Drew Adams's message of "Sun, 31 Aug 2014 08:30:54 -0700 (PDT)")
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.
Wolfgang
next prev parent reply other threads:[~2014-09-01 18:45 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 [this message]
2014-09-01 19:08 ` Eli Zaretskii
2014-09-01 19:43 ` Wolfgang Jenkner
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=85mwajb2mx.fsf@iznogoud.viz \
--to=wjenkner@inode.at \
--cc=18367@debbugs.gnu.org \
--cc=drew.adams@oracle.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).