From xemacs-m  Sun Jan  5 16:07:04 1997
Received: from atreides.mindspring.com (qmailr@atreides.mindspring.com [204.180.142.236])
          by xemacs.cs.uiuc.edu (8.8.4/8.8.4) with SMTP
	  id QAA12668 for <xemacs-beta@xemacs.org>; Sun, 5 Jan 1997 16:07:03 -0600 (CST)
Received: (qmail 22355 invoked by uid 52477); 5 Jan 1997 22:07:06 -0000
Sender: sj@atreides.mindspring.com
To: XEmacs beta <xemacs-beta@xemacs.org>
Subject: Re: Lazy lock broken in b34
References: <199701050718.CAA08228@spacely.icd.teradyne.com> <199701051729.KAA02964@branagh.lanl.gov> <m2loa7vlau.fsf@altair.xemacs.org>
Mime-Version: 1.0 (generated by tm-edit 7.100)
Content-Type: text/plain; charset=US-ASCII
From: Sudish Joseph <sudish@mindspring.com>
Date: 05 Jan 1997 17:07:05 -0500
In-Reply-To: Steven L Baur's message of 05 Jan 1997 13:55:53 -0800
Message-ID: <yviarajzu67q.fsf@atreides.mindspring.com>
Lines: 14
X-Mailer: Red Gnus v0.78/XEmacs 20.0

Steven L Baur writes:
> Nothing Happens.  It's appears to have something to do with attaching
> to the command loop hooks.  Things get really weird when you attempt
> to get in the debugger.

Lazy-lock defines it's own versions of text-property-{any,not-all} for
XEmacs 19.11 and earlier.  These are superfluous and incorrect in
20.x.  This was really looking weird until I bumbled into the results
of (symbol-file 'text-property-any). :-)

BTW, it'd be nice if symbol-file was interactive.  It's very useful
while debugging.

-Sudish

