From: Drew Adams <drew.adams@oracle.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Alan Mackenzie <acm@muc.de>, emacs-devel@gnu.org
Subject: RE: feature request: text property to prevent font-locking
Date: Sun, 31 Aug 2014 14:07:51 -0700 (PDT) [thread overview]
Message-ID: <1b3d2a94-3a06-4090-9487-46d4653cf89d@default> (raw)
In-Reply-To: <jwvbnr0igfr.fsf-monnier+emacs@gnu.org>
> >> By, the way, these kinds of problems are the reason why I
> >> suggested adding "planes" to text-properties.
> >> It should be relatively easy to implement.
> >
> > Sorry, that's too vague for me. But I guess it further confirms
> > that I am not missing something simple.
>
> I suggested that there be several planes of properties, so font-lock
> would place its properties in the plane `font-lock' while other
> packages can use their own plane. Then you'd separately specify
> rules for how to merge the various planes (with rules that can
> be distinct for each kind of property). The merge of properties
> would not take place during redisplay but instead would take place
> when the properties are added/removed.
Doesn't sound particularly simple to use (can you say "usine a
gaz"?), even if it is "relatively easy to implement". But I admit
that I have only a vague notion of what you have in mind.
While waiting for your implementation of that multifaceted feature,
perhaps we can adopt the simple change I suggested? (A bug fix, IMO.)
But again, I'm OK with just continuing to use the fix in my code,
if Emacs doesn't want it.
next prev parent reply other threads:[~2014-08-31 21:07 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-28 21:18 feature request: text property to prevent font-locking Drew Adams
2014-08-30 9:27 ` Alan Mackenzie
2014-08-30 20:15 ` Drew Adams
2014-08-30 21:34 ` Thien-Thi Nguyen
2014-08-31 6:06 ` Drew Adams
2014-08-31 16:11 ` Drew Adams
2014-08-31 12:40 ` Stefan Monnier
2014-08-31 15:30 ` Drew Adams
2014-08-31 19:57 ` Stefan Monnier
2014-08-31 21:07 ` Drew Adams [this message]
2014-08-31 21:43 ` Alan Mackenzie
2014-09-01 1:37 ` Stephen J. Turnbull
2014-09-01 20:45 ` Stefan Monnier
2014-09-02 2:02 ` Stephen J. Turnbull
2014-09-02 2:33 ` Richard Stallman
2014-09-02 6:04 ` David Kastrup
2014-08-31 14:31 ` Wolfgang Jenkner
2014-08-31 16:03 ` Drew Adams
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=1b3d2a94-3a06-4090-9487-46d4653cf89d@default \
--to=drew.adams@oracle.com \
--cc=acm@muc.de \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).