From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Hrvoje Niksic Newsgroups: gmane.emacs.devel Subject: Re: new text property Date: Mon, 10 Jun 2002 15:32:50 +0200 Sender: emacs-devel-admin@gnu.org Message-ID: References: <1023607376.8184.1228.camel@space-ghost> <87adq3jp5y.fsf@tc-1-100.kawasaki.gol.ne.jp> NNTP-Posting-Host: localhost.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: main.gmane.org 1023716039 27065 127.0.0.1 (10 Jun 2002 13:33:59 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Mon, 10 Jun 2002 13:33:59 +0000 (UTC) Cc: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai =?iso-8859-15?q?Gro=DFjohann?=), emacs-devel@gnu.org, xemacs-design@xemacs.org Return-path: Original-Received: from quimby.gnus.org ([80.91.224.244]) by main.gmane.org with esmtp (Exim 3.33 #1 (Debian)) id 17HPJ1-00072Q-00 for ; Mon, 10 Jun 2002 15:33:59 +0200 Original-Received: from fencepost.gnu.org ([199.232.76.164]) by quimby.gnus.org with esmtp (Exim 3.12 #1 (Debian)) id 17HPfs-0000cY-00 for ; Mon, 10 Jun 2002 15:57:36 +0200 Original-Received: from localhost ([127.0.0.1] helo=fencepost.gnu.org) by fencepost.gnu.org with esmtp (Exim 3.34 #1 (Debian)) id 17HPIA-0001dP-00; Mon, 10 Jun 2002 09:33:06 -0400 Original-Received: from 212-84-246-077.trmd.net ([212.84.246.77] helo=florida.munich.redhat.com) by fencepost.gnu.org with esmtp (Exim 3.34 #1 (Debian)) id 17HPHv-0001aj-00; Mon, 10 Jun 2002 09:32:52 -0400 Original-Received: from hniksic by florida.munich.redhat.com with local (Exim 3.35 #1 (Debian)) id 17HPHu-0003m6-00; Mon, 10 Jun 2002 15:32:50 +0200 Original-To: Miles Bader X-Attribution: Hrvoje X-Face: &{dT~)Pu6V<0y?>3p$;@vh\`C7xB~A0T-J%Og)J,@-1%q6Q+, gs<-9M#&`I8cJp2b1{vPE|~+JE+gx;a7%BG{}nY^ehK1"q#rG O,Rn1A_Cy%t]V=Brv7h (Miles Bader's message of "10 Jun 2002 21:26:01 +0900") Original-Lines: 19 User-Agent: Gnus/5.090006 (Oort Gnus v0.06) XEmacs/21.4 (Common Lisp, i686-pc-linux) Errors-To: emacs-devel-admin@gnu.org X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.0.9 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Emacs development discussions. List-Unsubscribe: , List-Archive: Xref: main.gmane.org gmane.emacs.devel:4699 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:4699 Miles Bader 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.