From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Ian Zimmerman Newsgroups: gmane.emacs.help Subject: lazy-lock vs. jit-lock Date: Wed, 28 Dec 2005 23:03:46 -0800 (PST) Message-ID: <877j9otmem.fsf@gmail.com> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1135840082 17862 80.91.229.2 (29 Dec 2005 07:08:02 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Thu, 29 Dec 2005 07:08:02 +0000 (UTC) Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Thu Dec 29 08:07:59 2005 Return-path: 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 1ErrtA-0003JD-Vj for geh-help-gnu-emacs@m.gmane.org; Thu, 29 Dec 2005 08:07:53 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1ErruV-0007zN-Ri for geh-help-gnu-emacs@m.gmane.org; Thu, 29 Dec 2005 02:09:16 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Errqf-0007BW-Oc for help-gnu-emacs@gnu.org; Thu, 29 Dec 2005 02:05:18 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Errqc-0007Av-48 for help-gnu-emacs@gnu.org; Thu, 29 Dec 2005 02:05:15 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Errqa-0007AT-6v for help-gnu-emacs@gnu.org; Thu, 29 Dec 2005 02:05:12 -0500 Original-Received: from [64.233.184.207] (helo=wproxy.gmail.com) by monty-python.gnu.org with esmtp (Exim 4.34) id 1Errqt-0005YG-35 for help-gnu-emacs@gnu.org; Thu, 29 Dec 2005 02:05:31 -0500 Original-Received: by wproxy.gmail.com with SMTP id 70so1330875wra for ; Wed, 28 Dec 2005 23:03:47 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:to:subject:from:message-id:lines:user-agent:mime-version:content-type:date; b=s5egO7X9Q/zUHl1IuqGBoYopTWsjl+fE9Qbfp+Wna7uQs8Lkk1UPdluF1JjBYQN6vV824oFKSG+1QVH1nV3KiC31uF6EsFmpCs9N0U6TaWKfsqhfxEyjGGWaDipA6JhCUdzkY2Amxz5wSuVGpoFBkA7Z2Ic5DDZ7Adbw13qrkCY= Original-Received: by 10.64.213.9 with SMTP id l9mr3451058qbg; Wed, 28 Dec 2005 23:03:47 -0800 (PST) Original-Received: from unicorn ( [72.60.106.112]) by mx.gmail.com with ESMTP id f13sm3328065qba.2005.12.28.23.03.46; Wed, 28 Dec 2005 23:03:46 -0800 (PST) Original-Received: from itz by unicorn with local (Exim 4.60) (envelope-from ) id 1ErrpB-00015r-Ic; Thu, 29 Dec 2005 02:03:45 -0500 Original-To: help-gnu-emacs@gnu.org Original-Lines: 13 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.4 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:32279 Archived-At: Can anyone comment on the relative advantages of these kinds of font-locking? jit-lock seems to be the default in Emacs 21.4, but I fount that in some buffers (not necessarily large ones) whole chunks are left unfontified. Waiting for them to be "stealthily" fontified also doesn't help; only font-lock-fontify-buffer does. Customizing font-lock-support-mode and setting it to lazy-lock-mode eliminates the problem. So I'd just like to know what I'm missing this way. -- A true pessimist won't be discouraged by a little success.