From: Colin Walters <walters@gnu.org>
Subject: new text property
Date: 09 Jun 2002 03:22:56 -0400 [thread overview]
Message-ID: <1023607376.8184.1228.camel@space-ghost> (raw)
Hello,
Emacs 21.4 will have a new text property `font-lock-face'. I would
personally like to see support for this property in XEmacs too, so the
authors of externally distributed modes can use it easily and keep their
code portable, and also to keep Emacs and XEmacs from diverging more.
The rationale for this change is that it easily allows "special" modes
to have their fontification controlled by M-x font-lock-mode, rather
than having to set a variable like `cvs-highlight', `Info-fontify', or
tracking down a -face variable and setting it to `default'.
Emacs actually doesn't implement this variable in the core C code;
instead, we added a new variable `char-property-alias-alist' which
allows properties to have alternative names. M-x font-lock-mode can
then add and delete `font-lock-face' as an alias for the `face'
property. There are other neat things one can do with this variable
too.
It would be nice if XEmacs could support `char-property-alias-alist' in
its entirety (I bet all you need to change is `extent-get'), but I'd be
satisfied with just implementing support for `font-lock-face', however
you choose to do it.
What do you (XEmacs people) think?
If you're interested in all the details of how we eventually arrived at
this solution, see the thread entited "kill ring menu" on emacs-devel
(we really should have chosen a different subject title at some
point...).
next reply other threads:[~2002-06-09 7:22 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-09 7:22 Colin Walters [this message]
2002-06-10 4:29 ` new text property Stephen J. Turnbull
[not found] ` <87y9dnycw8.fsf@tleepslib.sk.tsukuba.ac.jp>
2002-06-10 5:12 ` Miles Bader
2002-06-10 5:46 ` Colin Walters
[not found] ` <buod6uzbtun.fsf@mcspd15.ucom.lsi.nec.co.jp>
2002-06-10 6:38 ` Stephen J. Turnbull
[not found] ` <87bsajy6y8.fsf@tleepslib.sk.tsukuba.ac.jp>
2002-06-10 6:53 ` Colin Walters
2002-06-10 14:30 ` Stefan Monnier
[not found] ` <200206101431.g5AEV0G28267@rum.cs.yale.edu>
2002-06-10 17:35 ` Adrian Aichner
2002-06-11 5:07 ` Eli Zaretskii
2002-06-11 8:24 ` Stephen J. Turnbull
2002-06-10 8:50 ` Hrvoje Niksic
2002-06-10 11:16 ` Kai Großjohann
2002-06-10 12:07 ` Hrvoje Niksic
2002-06-10 12:26 ` Miles Bader
2002-06-10 13:32 ` Hrvoje Niksic
2002-06-10 14:28 ` Stefan Monnier
2002-06-10 15:08 ` Kai Großjohann
2002-06-10 18:51 ` Colin Walters
[not found] ` <1023735066.26240.14.camel@space-ghost>
2002-06-11 11:40 ` Hrvoje Niksic
2002-06-11 19:47 ` Colin Walters
2002-06-11 20:40 ` Hrvoje Niksic
2002-06-12 8:18 ` Kai Großjohann
2002-06-12 9:05 ` Miles Bader
2002-06-12 1:14 ` Stephen J. Turnbull
[not found] ` <877kl5pabc.fsf@tleepslib.sk.tsukuba.ac.jp>
2002-06-12 3:11 ` Colin Walters
2002-06-12 8:16 ` Stephen J. Turnbull
2002-06-12 17:46 ` Adrian Aichner
2002-06-10 15:03 ` Kai Großjohann
[not found] ` <vaf1ybf18hp.fsf@INBOX.auto.emacs.devel.tok.lucy.cs.uni-dortmund.de>
2002-06-10 15:13 ` Hrvoje Niksic
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=1023607376.8184.1228.camel@space-ghost \
--to=walters@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).