From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Robert Thorpe" Newsgroups: gmane.emacs.help Subject: Re: font-lock support mode in emacs 22 Date: 6 Dec 2006 10:12:05 -0800 Organization: http://groups.google.com Message-ID: <1165428725.358533.205680@j44g2000cwa.googlegroups.com> References: <1165328561.281870.161210@73g2000cwn.googlegroups.com> NNTP-Posting-Host: dough.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Trace: sea.gmane.org 1165430499 24427 80.91.229.10 (6 Dec 2006 18:41:39 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Wed, 6 Dec 2006 18:41:39 +0000 (UTC) Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Wed Dec 06 19:41:38 2006 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by dough.gmane.org with esmtp (Exim 4.50) id 1Gs1hu-0002QW-DX for geh-help-gnu-emacs@m.gmane.org; Wed, 06 Dec 2006 19:41:26 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Gs1ht-00086E-Sa for geh-help-gnu-emacs@m.gmane.org; Wed, 06 Dec 2006 13:41:25 -0500 Original-Path: shelby.stanford.edu!newsfeed.stanford.edu!postnews.google.com!j44g2000cwa.googlegroups.com!not-for-mail Original-Newsgroups: gnu.emacs.help Original-Lines: 19 Original-NNTP-Posting-Host: 213.94.228.210 Original-X-Trace: posting.google.com 1165428730 24769 127.0.0.1 (6 Dec 2006 18:12:10 GMT) Original-X-Complaints-To: groups-abuse@google.com Original-NNTP-Posting-Date: Wed, 6 Dec 2006 18:12:10 +0000 (UTC) In-Reply-To: <1165328561.281870.161210@73g2000cwn.googlegroups.com> User-Agent: G2/1.0 X-HTTP-UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6,gzip(gfe),gzip(gfe) X-HTTP-Via: 1.0 EMF3ASPROXY03 Complaints-To: groups-abuse@google.com Injection-Info: j44g2000cwa.googlegroups.com; posting-host=213.94.228.210; posting-account=hWoAPxMAAAAnBKSBz1ZivwUPPjEuve7bvVCHZQ8rhrluPfwcBJd92w Original-Xref: shelby.stanford.edu gnu.emacs.help:143690 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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:39292 Archived-At: spamfilteraccount@gmail.com wrote: > I just checked in cvs > (http://cvs.savannah.gnu.org/viewcvs/emacs/lisp/font-lock.el?rev=1.308&root=emacs&view=auto) > that font-lock-support-mode is still 'jit-lock-mode in emacs 22. > > Is this still necessary? I mean we have pretty fast machines in these > days, so couldn't emacs perform the fontification in realtime? Did the > subject come up on emacs-devel during development of emacs 22? Incremental syntax highlighting is always useful, because it allows ever bigger files to be opened. At present I experience pauses fontifying say ~300kb files. It would be nice if with faster machines this didn't happen. Doing it in realtime would prevent this from happening. It would also prevent using more sophisticated regexp, at present many modes optimize their regexp for speed. I think the problem you're experiencing it your code is caused because it does things in a rather unusual way.