From xemacs-m  Wed Aug 13 02:21:51 1997
Received: from lemming0.lem.uni-karlsruhe.de (jens@lemming0.lem.uni-karlsruhe.de [129.13.103.195])
	by xemacs.org (8.8.5/8.8.5) with ESMTP id CAA08034
	for <xemacs-beta@xemacs.org>; Wed, 13 Aug 1997 02:21:50 -0500 (CDT)
Received: (from jens@localhost)
	by lemming0.lem.uni-karlsruhe.de (8.8.5/8.8.5) id JAA15257;
	Wed, 13 Aug 1997 09:21:49 +0200
To: XEmacs Beta List <xemacs-beta@xemacs.org>
Subject: Re: lazy-lock?
References: <ocren7zce0a.fsf@ml.com>
X-Face: Z[@OB)("ZvE?ev~1b+b!0ZUB.$%rh.9qE>dVf>q}Q/V?%d`J3gd!LR\aAZ8<Hwi]xTA(:*c;i3,?K?+rCy*^b$)a,}E?eo},}x2]5LlJysyoUOK"o[>K)'\Ulb7y-7*.If^;rHl['oa)n_M7E6w+LDKMs"G8_`c)uOS1^}.1|8Ill]7X68X-paeUOpBhz<F`B0?~^2Et~GYfw~/0]H]nx4~C_E/_mp#^7Ixc:
Reply-To: jens@lemming0.lem.uni-karlsruhe.de
Mime-Version: 1.0 (generated by tm-edit 7.106)
Content-Type: text/plain; charset=US-ASCII
From: Jens Lautenbacher <jens@lemming0.lem.uni-karlsruhe.de>
Date: 13 Aug 1997 09:21:49 +0200
In-Reply-To: Colin Rafferty's message of 12 Aug 1997 17:01:09 -0400
Message-ID: <x2203y35v6.fsf@lemming0.lem.uni-karlsruhe.de>
Lines: 40
X-Mailer: Gnus v5.4.52/XEmacs 20.2

Colin Rafferty <craffert@ml.com> writes:

> [1  <text/plain; US-ASCII (7bit)>]
> Hi-
> 
> Maybe I am just not paying attention, but lazy-lock doesn't seem to work 
> in 20.3, and hasn't worked for a while.
> 
> It seems as though it is fontifying the entire buffer when I load one
> in.
> 
> Is it just me?  This is what I use (and checked separately with xemacs -q):
> 
> [2 hoho.el <application/octet-stream>]
> 
> (setq font-lock-maximum-decoration t)
> (setq lazy-lock-stealth-time nil)
> (setq lazy-lock-hide-invisible nil)
> (require 'font-lock)
> (require 'lazy-lock)
> (add-hook 'font-lock-mode-hook 'turn-on-lazy-lock)
> 
> [3  <text/plain; US-ASCII (7bit)>]
> -- 
> Colin

The problem is with (setq lazy-lock-hide-invisible nil) The now again
enabled XEmacs implementation ("Ben's version") of lazy-lock is
broken IMHO. The other version which was enabled during some period of 
time until around 4 or 5 betas work OK with a minor glitch that
fontification would only start if any action would take place in the
buffer (like a button click, key press....). But this could also be
regarded as  a feature... 

I voluntered to look at the different font-lock issues, but I was in
hospital for some time and am now in the process of doing a pile of my
real work :-( I hope I can get around to this soon.

     jtl

