From mboxrd@z Thu Jan  1 00:00:00 1970
Path: news.gmane.org!not-for-mail
From: spamfilteraccount@gmail.com
Newsgroups: gmane.emacs.help
Subject: Re: Using syntax info for font-locking?
Date: 28 Oct 2006 07:14:03 -0700
Organization: http://groups.google.com
Message-ID: <1162044843.176347.283030@b28g2000cwb.googlegroups.com>
References: <1161981827.499222.259570@k70g2000cwa.googlegroups.com>
	<mailman.329.1162024023.27805.help-gnu-emacs@gnu.org>
NNTP-Posting-Host: main.gmane.org
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
X-Trace: sea.gmane.org 1162046433 6581 80.91.229.2 (28 Oct 2006 14:40:33 GMT)
X-Complaints-To: usenet@sea.gmane.org
NNTP-Posting-Date: Sat, 28 Oct 2006 14:40:33 +0000 (UTC)
Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Sat Oct 28 16:40:31 2006
Return-path: <help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org>
Envelope-to: geh-help-gnu-emacs@m.gmane.org
Original-Received: from lists.gnu.org ([199.232.76.165])
	by ciao.gmane.org with esmtp (Exim 4.43)
	id 1GdpMG-0006ld-HQ
	for geh-help-gnu-emacs@m.gmane.org; Sat, 28 Oct 2006 16:40:25 +0200
Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43)
	id 1GdpMF-0004Dq-Uu
	for geh-help-gnu-emacs@m.gmane.org; Sat, 28 Oct 2006 10:40:23 -0400
Original-Path: shelby.stanford.edu!newsfeed.stanford.edu!postnews.google.com!b28g2000cwb.googlegroups.com!not-for-mail
Original-Newsgroups: gnu.emacs.help
Original-Lines: 16
Original-NNTP-Posting-Host: 81.183.147.247
Original-X-Trace: posting.google.com 1162044850 10912 127.0.0.1 (28 Oct 2006 14:14:10
	GMT)
Original-X-Complaints-To: groups-abuse@google.com
Original-NNTP-Posting-Date: Sat, 28 Oct 2006 14:14:10 +0000 (UTC)
In-Reply-To: <mailman.329.1162024023.27805.help-gnu-emacs@gnu.org>
User-Agent: G2/1.0
X-HTTP-UserAgent: Opera/9.01 (Windows NT 5.0; U; en),gzip(gfe),gzip(gfe)
Complaints-To: groups-abuse@google.com
Injection-Info: b28g2000cwb.googlegroups.com; posting-host=81.183.147.247;
	posting-account=b98TkQ0AAAD7PsllN8gfWGRoPOPWdnv4
Original-Xref: shelby.stanford.edu gnu.emacs.help:142735
Original-To: help-gnu-emacs@gnu.org
X-BeenThere: help-gnu-emacs@gnu.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Users list for the GNU Emacs text editor <help-gnu-emacs.gnu.org>
List-Unsubscribe: <http://lists.gnu.org/mailman/listinfo/help-gnu-emacs>,
	<mailto:help-gnu-emacs-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/help-gnu-emacs>
List-Post: <mailto:help-gnu-emacs@gnu.org>
List-Help: <mailto:help-gnu-emacs-request@gnu.org?subject=help>
List-Subscribe: <http://lists.gnu.org/mailman/listinfo/help-gnu-emacs>,
	<mailto:help-gnu-emacs-request@gnu.org?subject=subscribe>
Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org
Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org
Xref: news.gmane.org gmane.emacs.help:38354
Archived-At: <http://permalink.gmane.org/gmane.emacs.help/38354>


Dieter Wilhelm wrote:
> But
> at my state of knowledge the consequence of this "dynamic"
> font-locking means to check after *any* self inserting key the whole
> file and re-fontify it.

The process could probably be optimized by determining the smallest
possible region of the file which can be affected by the last change
and then comparing the syntactic information in this region with the
previous information and performing only those highlighting changes
which are necessary.

I imagine also the current font lock implementation performs only local
checks and doesn't refontify the whole file at every change.