From xemacs-m  Wed Aug 13 10:47:03 1997
Received: from wfdutilgw.ml.com (wfdutilf01.ml.com [206.3.74.31])
	by xemacs.org (8.8.5/8.8.5) with ESMTP id KAA23514
	for <xemacs-beta@xemacs.org>; Wed, 13 Aug 1997 10:47:03 -0500 (CDT)
Received: from ml1.ml.com ([199.201.57.130])
	by wfdutilgw.ml.com (8.8.5/8.8.5/MLgw-3.03) with ESMTP id LAA15894
	for <xemacs-beta@xemacs.org>; Wed, 13 Aug 1997 11:41:46 -0400 (EDT)
Received: from commpost.ml.com (commpost.ml.com [146.125.4.24])
	by ml1.ml.com (8.8.5/8.8.5/MLml4-2.07) with SMTP id LAA09830
	for <xemacs-beta@xemacs.org>; Wed, 13 Aug 1997 11:46:27 -0400 (EDT)
Received: from spssunp.spspme.ml.com (spssunp.spspme.ml.com [192.168.111.13]) by commpost.ml.com (8.6.12/8.6.12) with ESMTP id LAA19181 for <xemacs-beta@xemacs.org>; Wed, 13 Aug 1997 11:51:32 -0400
Received: by spssunp.spspme.ml.com (SMI-8.6/SMI-4.1)
	id LAA18296; Wed, 13 Aug 1997 11:46:33 -0400
To: XEmacs Beta List <xemacs-beta@xemacs.org>
Subject: Re: lazy-lock?
References: <ocren7zce0a.fsf@ml.com> <x2203y35v6.fsf@lemming0.lem.uni-karlsruhe.de>
X-Face: D>:hrrB{l6#\wU;)0R:OHSTA@ayd.Oq?s@Rrc;[+z0m+<-U"$G-J6L)F2QY`qK~uPu!s1(6{\#uy!Ag/D)?'L[}xErXvxoPn8T_hKi{M]/(`BF{e}X7;hby`p\.E$rJ}Aff#BT,rdDIw\y
X-Y-Zippy: I always liked FLAG DAY!!
Mime-Version: 1.0 (generated by tm-edit 7.108)
Content-Type: text/plain; charset=US-ASCII
From: Colin Rafferty <craffert@ml.com>
Date: 13 Aug 1997 11:46:32 -0400
In-Reply-To: Jens Lautenbacher's message of "13 Aug 1997 09:21:49 +0200"
Message-ID: <ocr90y6cch3.fsf@ml.com>
Lines: 35
X-Mailer: Gnus v5.4.64/XEmacs 20.3(beta17) - "Bucharest"

Jens Lautenbacher writes:
> Colin Rafferty <craffert@ml.com> writes:

>> 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):

>> (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)

> The problem is with (setq lazy-lock-hide-invisible nil)

That is exactly it.  I tried setting it back to `t', and everything was
cool.

> 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.

I have gotten a little motivation, and I am looking into it.  So far, it 
looks as though there is an inconsistent state during the pre-idle-hook
call after a file is found but before it is displayed.

I am investigating.

-- 
Colin

