From xemacs-m  Tue Feb 25 09:03:04 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 JAA05032
	for <xemacs-beta@xemacs.org>; Tue, 25 Feb 1997 09:00:16 -0600 (CST)
Received: from mail.esrin.esa.it (plod.esrin.esa.it) by maes.esrin.esa.it with SMTP id AA15493
  (5.65c/IDA-1.4.4 for <xemacs-beta@xemacs.org>); Tue, 25 Feb 1997 16:00:02 +0100
Received: from penelope.esa.it by mail.esrin.esa.it (4.1/SMI-4.1)
	id AA17458; Tue, 25 Feb 97 15:00:04 GMT
Date: Tue, 25 Feb 97 15:00:04 GMT
Message-Id: <9702251500.AA17458@mail.esrin.esa.it>
Received: by penelope.esa.it (4.1/SMI-4.1)
	id AA14215; Tue, 25 Feb 97 16:04:46 +0100
From: Simon Marshall <Simon.Marshall@esrin.esa.it>
To: XEmacs Beta <xemacs-beta@xemacs.org>
In-Reply-To: <199702251433.JAA09103@spacely.icd.teradyne.com> (message from
	Vinnie Shelton on Tue, 25 Feb 1997 09:33:44 -0500)
Subject: Re: [19.15-b95 / 20.1-b2] lazy-lock lossage?
Reply-To: Simon Marshall <Simon.Marshall@esrin.esa.it>

Vin> If lazy-lock is not on for the buffer (ie if the buffer is too
Vin> small), the options item is not selected.  This is, IMO, a bug,
Vin> because when a user first enables lazy-lock in say, the scratch
Vin> buffer, the option item is not selected.  I have always found this
Vin> confusing.

Yes, that's true.  One fix would be to make its menu entry unselectable if
Lazy Lock mode (and Fast Lock mode) wouldn't be turned on, i.e., the
buffer is too small.

To be honest, I don't think the options for Lazy Lock mode and Fast Lock
mode are any use, since when you can turn them on it's already too late as
the buffer got fontified.  The options also do more than one thing; they
turn on/off in the current buffer, and enable/disable for all future
buffers.  I find that confusing; I turn on something I don't expect to get
it everywhere.

But, YMMV.  Si.

