From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Colin Walters Newsgroups: gmane.emacs.devel Subject: Re: new text property Date: 10 Jun 2002 02:53:33 -0400 Sender: emacs-devel-admin@gnu.org Message-ID: <1023692013.1593.1404.camel@space-ghost> References: <1023607376.8184.1228.camel@space-ghost> <87y9dnycw8.fsf@tleepslib.sk.tsukuba.ac.jp> <87bsajy6y8.fsf@tleepslib.sk.tsukuba.ac.jp> NNTP-Posting-Host: localhost.gmane.org Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Trace: main.gmane.org 1023692617 30637 127.0.0.1 (10 Jun 2002 07:03:37 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Mon, 10 Jun 2002 07:03:37 +0000 (UTC) Return-path: Original-Received: from quimby.gnus.org ([80.91.224.244]) by main.gmane.org with esmtp (Exim 3.33 #1 (Debian)) id 17HJDF-0007y2-00 for ; Mon, 10 Jun 2002 09:03:37 +0200 Original-Received: from fencepost.gnu.org ([199.232.76.164]) by quimby.gnus.org with esmtp (Exim 3.12 #1 (Debian)) id 17HJZy-0000HD-00 for ; Mon, 10 Jun 2002 09:27:06 +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 17HJCj-0002Nx-00; Mon, 10 Jun 2002 03:03:05 -0400 Original-Received: from monk.debian.net ([216.185.54.61] helo=monk.verbum.org) by fencepost.gnu.org with esmtp (Exim 3.34 #1 (Debian)) id 17HJAG-0002LM-00 for ; Mon, 10 Jun 2002 03:00:32 -0400 Original-Received: from space-ghost.verbum.private (freedom.cis.ohio-state.edu [164.107.60.183]) (using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits)) (Client CN "space-ghost.verbum.org", Issuer "monk.verbum.org" (verified OK)) by monk.verbum.org (Postfix (Debian/GNU)) with ESMTP id 6ABED74000BA; Mon, 10 Jun 2002 03:00:31 -0400 (EDT) Original-Received: by space-ghost.verbum.private (Postfix (Debian/GNU), from userid 1000) id 4AC208AD826; Mon, 10 Jun 2002 02:53:34 -0400 (EDT) Original-To: emacs-devel@gnu.org, xemacs-design@gnu.org In-Reply-To: <87bsajy6y8.fsf@tleepslib.sk.tsukuba.ac.jp> X-Mailer: Ximian Evolution 1.0.3 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:4684 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:4684 On Mon, 2002-06-10 at 02:38, Stephen J. Turnbull wrote: > What I do know is that font-lock itself has a minimum of five > implementations (font-lock, font-lock-cache, lazy-lock, lazy-shot, and > jit-lock). Those are all ways of dynamically searching for text and placing `face' properties on them. That's a very different approach from the way `font-lock-face' is used. Really, `font-lock-face' has nothing to do with what people traditionally think of as "Font Lock" (i.e. regexps, searching), except that it happens to be toggled on and off when the user types M-x font-lock-mode. The amount of code dealing with `font-lock-face' in font-core.el amounts to about 8 lines. > Primitive highlighting has at least three interfaces > (overlays, text properties, extents). This looks like an area ripe > for consolidation, not proliferation, of APIs to me. Yes, but adding `char-property-alias-alist' will not really increase the difference between interfaces. XEmacs appears to already have `default-text-properties', which is similar. > I also don't like the idea that semantics apparently depend on whether > a reference is an "original" or an "alias". They don't. > Thus the warning. This may be the right thing to do, but I want to > make sure that XEmacs people _discuss_ this change rather than simply > adopt it for the sake of compatibility. I understand that. But could you please study `font-lock-face' a little bit more carefully? The points you have raised so far don't really apply to it.