From: Hrvoje Niksic <hniksic@xemacs.org>
Cc: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann),
emacs-devel@gnu.org, xemacs-design@xemacs.org
Subject: Re: new text property
Date: Mon, 10 Jun 2002 15:32:50 +0200 [thread overview]
Message-ID: <sxselff9s3h.fsf@florida.munich.redhat.com> (raw)
In-Reply-To: <87adq3jp5y.fsf@tc-1-100.kawasaki.gol.ne.jp> (Miles Bader's message of "10 Jun 2002 21:26:01 +0900")
Miles Bader <miles@gnu.org> writes:
> Don't get hung up on the traditional conflation of the font-lock UI
> with the mechanism used to implement it; it's really not necessary.
Why not? Font-lock is not only about the hairy regexps that implement
it; it's also about respecting the settings for font-lock-*-face and
variables such as font-lock-maximum-decoration,
font-lock-auto-fontify, font-lock-maximum-size, etc. A highlighting
mechanism that doesn't respect any of those has no reason to be bound
by `M-x font-lock-mode' either.
I'm not a font-lock hacker, I just think that overloading the meaning
of `M-x font-lock-mode' might not be such a good idea. Confusing the
two will lead people to try to use other font-lock settings in
non-font-lock environments, and that will silently fail.
So, between your choices of (1) and (2), either is OK if done right.
But I'd rather leave things as they are than do the wrong thing.
next prev parent reply other threads:[~2002-06-10 13:32 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-09 7:22 new text property Colin Walters
2002-06-10 4:29 ` 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 [this message]
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=sxselff9s3h.fsf@florida.munich.redhat.com \
--to=hniksic@xemacs.org \
--cc=Kai.Grossjohann@CS.Uni-Dortmund.DE \
--cc=emacs-devel@gnu.org \
--cc=xemacs-design@xemacs.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).