From xemacs-m  Tue Feb 25 09:27:28 1997
Received: from steadfast.teradyne.com (steadfast.teradyne.com [131.101.1.200])
	by xemacs.org (8.8.5/8.8.5) with ESMTP id JAA05238
	for <xemacs-beta@xemacs.org>; Tue, 25 Feb 1997 09:27:27 -0600 (CST)
Received: from kiki.icd.teradyne.com (kiki.icd.teradyne.com [131.101.1.30]) by steadfast.teradyne.com (8.7.1/8.7.1) with ESMTP id KAA05644 for <xemacs-beta@xemacs.org>; Tue, 25 Feb 1997 10:30:43 -0500 (EST)
Received: from spacely.icd.teradyne.com (spacely.icd.teradyne.com [131.101.10.9]) by kiki.icd.teradyne.com (8.7.1/8.7.1) with SMTP id KAA05800 for <xemacs-beta@xemacs.org>; Tue, 25 Feb 1997 10:24:26 -0500 (EST)
Received: from spacely by spacely.icd.teradyne.com (SMI-8.6/SMI-SVR4)
	id KAA09392; Tue, 25 Feb 1997 10:27:21 -0500
Message-Id: <199702251527.KAA09392@spacely.icd.teradyne.com>
X-Mailer: exmh version 2.0gamma 1/27/96
To: XEmacs Beta <xemacs-beta@xemacs.org>
Subject: Re: [19.15-b95 / 20.1-b2] lazy-lock lossage? 
In-reply-to: Simon.Marshall's message of Tue, 25 Feb 1997 15:00:04 +0000.
	     <9702251500.AA17458@mail.esrin.esa.it> 
reply-to: acs@acm.org
X-Attribution: Vin
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Tue, 25 Feb 1997 10:27:21 -0500
From: Vinnie Shelton  <shelton@icd.teradyne.com>


I agree that this dual function is the source of the confusion.  i
think it's a general problem - some options are global and some are
local to the buffer or frame.  I don't really know what to do about
this, though.

vin

>>>>> On Tue, 25 Feb 97, Simon Marshall <Simon.Marshall@esrin.esa.it> said:

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.

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

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

Simon> But, YMMV.  Si.



