From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Alan Mackenzie Newsgroups: gmane.emacs.help Subject: Re: What is the _essential_ difference between lazy-lock and jit-lock? Date: Fri, 23 Jan 2004 22:34:59 +0000 Organization: muc.de e.V. -- private internet access Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Message-ID: References: <9f3pub.9a.ln@acm.acm> <94lpub.q5.ln@acm.acm> NNTP-Posting-Host: deer.gmane.org X-Trace: sea.gmane.org 1074932200 12927 80.91.224.253 (24 Jan 2004 08:16:40 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sat, 24 Jan 2004 08:16:40 +0000 (UTC) Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Sat Jan 24 09:16:32 2004 Return-path: Original-Received: from monty-python.gnu.org ([199.232.76.173]) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1AkIy0-0002nv-00 for ; Sat, 24 Jan 2004 09:16:32 +0100 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.24) id 1AkIxU-0006Ut-9K for geh-help-gnu-emacs@m.gmane.org; Sat, 24 Jan 2004 03:16:00 -0500 Original-Path: shelby.stanford.edu!newsfeed.stanford.edu!news.tele.dk!news.tele.dk!small.news.tele.dk!news-FFM2.ecrc.net!newsfeed.stueberl.de!news.space.net!news.muc.de!not-for-mail Original-Newsgroups: gnu.emacs.help Original-Lines: 53 Original-NNTP-Posting-Host: acm.muc.de Original-X-Trace: marvin.muc.de 1074931358 74078 193.149.49.134 (24 Jan 2004 08:02:38 GMT) Original-X-Complaints-To: news-admin@muc.de Original-NNTP-Posting-Date: 24 Jan 2004 08:02:38 GMT User-Agent: tin/1.4.5-20010409 ("One More Nightmare") (UNIX) (Linux/2.0.35 (i686)) Original-Xref: shelby.stanford.edu gnu.emacs.help:120374 Original-To: help-gnu-emacs@gnu.org X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.2 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: main.gmane.org gmane.emacs.help:16318 X-Report-Spam: http://spam.gmane.org/gmane.emacs.help:16318 Eli Zaretskii wrote on Fri, 23 Jan 2004 13:42:53 +0200: >> From: Alan Mackenzie >> Surely not - Emacs _HUNG_ with stealth fontification, accepting no >> keypresses (apart from a double C-g), and remained in this state >> overnight (> 8 hours). > I think these problems were solved in the meantime (IIRC, they were due > to bad interaction between JIT lock and font-lock definitions for some > modes). Any chance of a revision number (presumably of jit-lock.el) where this was fixed? > Please try again and see if you still have such problems. I've set font-lock-support-mode back to jit-, and I've been trying all evening ;-) With Emacs 21.1, I've had my Emacs lock up just once. Loading jit-lock.elc V1.31 (the latest from savannah), I've not triggered the problem. Not yet. I'll try loading a few more buffers to see if that makes things worse. [ .... ] >> Perhaps what is wanted is a command like `(font-lock-tune-font-lock >> 'low-powered-workstation)' by which users could select from amongst >> several pre-defined tunings, somewhat analogous to CC Mode's >> `c-set-style'. > I have a better idea of a user interface: > (font-lock-tune-font-lock 'my-specific-preferences) > or > (font-lock-tune-font-lock 'my-favorite-computer) > Seriously, though: that's the first time I hear an Emacs veteran > complain about too many customization options. Surely, you should > know that they all exist for a good purpose. I wasn't meaning to suggest that they should be removed. Merely that they should be supplemented with a more handy higher level tool, leaving the individual options available for specific needs/wants. > Perhaps you want to say that their documentation needs some work--that > is something I could understand. That too. -- Alan Mackenzie (Munich, Germany) Email: aacm@muuc.dee; to decode, wherever there is a repeated letter (like "aa"), remove half of them (leaving, say, "a").