From xemacs-m  Tue Feb 25 03:40:28 1997
Received: from maes.esrin.esa.it (maes.esrin.esa.it [192.106.252.50])
	by xemacs.org (8.8.5/8.8.5) with SMTP id DAA27825
	for <xemacs-beta@xemacs.org>; Tue, 25 Feb 1997 03:40:26 -0600 (CST)
Received: from mail.esrin.esa.it (plod.esrin.esa.it) by maes.esrin.esa.it with SMTP id AA11948
  (5.65c/IDA-1.4.4 for <xemacs-beta@xemacs.org>); Tue, 25 Feb 1997 10:40:26 +0100
Received: from penelope.esa.it by mail.esrin.esa.it (4.1/SMI-4.1)
	id AA14484; Tue, 25 Feb 97 09:40:26 GMT
Date: Tue, 25 Feb 97 09:40:26 GMT
Message-Id: <9702250940.AA14484@mail.esrin.esa.it>
Received: by penelope.esa.it (4.1/SMI-4.1)
	id AA13841; Tue, 25 Feb 97 10:45:07 +0100
From: Simon Marshall <Simon.Marshall@esrin.esa.it>
To: XEmacs Beta <xemacs-beta@xemacs.org>
In-Reply-To: <vk67zhvr5f.fsf@cdc.noaa.gov> (message from Mark Borges on 24 Feb
	1997 14:19:08 -0700)
Subject: Re: [19.15-b95 / 20.1-b2] lazy-lock lossage?
Reply-To: Simon Marshall <Simon.Marshall@esrin.esa.it>

mb> Something bizarre is going on with lazy-lock and font-locking of
mb> compilation buffers. For instance, visiting the efs directory and then
mb> doing `M-x grep -in highlight dired*.el' (never mind what I was
mb> looking for ;-), gives this bogus answer (cut out of the *grep*
mb> buffer):

mb>    cd /home/mdb/gnu/lib/xemacs-20.1-b2/lisp/efs/
mb>    grep -in highlight dired*.el /dev/null

mb>    grep finished (matches found) at Mon Feb 24 14:00:29

Sorry, I can't reproduce this.

Note that normally Lazy Lock mode would not be turned on in the *grep*
buffer because the buffer is less than lazy-lock-minimum-size when Font
Lock mode is turned on.

The same goes for the problem reported for *shell* mode.

You can find out if Lazy Lock mode is actually turned on in some buffer by
looking at the lazy-lock-mode variable.

Ta, Si.

BTW, today is Pass The Buck day in Italy (in honour of San Passobucko).

