From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: "Stefan Monnier" Newsgroups: gmane.emacs.devel Subject: Re: new text property Date: Mon, 10 Jun 2002 10:28:37 -0400 Sender: emacs-devel-admin@gnu.org Message-ID: <200206101428.g5AESbL28221@rum.cs.yale.edu> 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 1023719445 9497 127.0.0.1 (10 Jun 2002 14:30:45 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Mon, 10 Jun 2002 14:30:45 +0000 (UTC) Cc: Miles Bader , 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 17HQBw-0002T4-00 for ; Mon, 10 Jun 2002 16:30:44 +0200 Original-Received: from fencepost.gnu.org ([199.232.76.164]) by quimby.gnus.org with esmtp (Exim 3.12 #1 (Debian)) id 17HQYo-0001nZ-00 for ; Mon, 10 Jun 2002 16:54:23 +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 17HQBS-0008Sj-00; Mon, 10 Jun 2002 10:30:14 -0400 Original-Received: from rum.cs.yale.edu ([128.36.229.169]) by fencepost.gnu.org with esmtp (Exim 3.34 #1 (Debian)) id 17HQ9x-00088T-00; Mon, 10 Jun 2002 10:28:41 -0400 Original-Received: (from monnier@localhost) by rum.cs.yale.edu (8.11.6/8.11.6) id g5AESbL28221; Mon, 10 Jun 2002 10:28:37 -0400 X-Mailer: exmh version 2.4 06/23/2000 with nmh-1.0.4 Original-To: Hrvoje Niksic 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:4702 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:4702 > > 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. You forgot jit-lock (aka lazy-shot). > A highlighting > mechanism that doesn't respect any of those has no reason to be bound > by `M-x font-lock-mode' either. Agreed. I proposed a new `highlighting-mode' (or some other name, I can't remember) instead of moving code out of font-lock.el to font-core.el (I hate moving code, among other things because it makes CVS much less useful) but for some reason it was not retained. I didn't (and still don't) have time/energy to follow the whole discussion, tho. Stefan "font-lock hacker"