From xemacs-m  Thu Feb 27 10:03:26 1997
Received: from neal.ctd.comsat.com (exim@neal.ctd.comsat.com [134.133.40.21])
	by xemacs.org (8.8.5/8.8.5) with SMTP id KAA04315
	for <xemacs-beta@xemacs.org>; Thu, 27 Feb 1997 10:03:25 -0600 (CST)
Received: from neal by neal.ctd.comsat.com with local (Exim 1.58 #2)
	id 0w08HS-00026b-00; Thu, 27 Feb 1997 11:02:02 -0500
To: Simon Marshall <Simon.Marshall@esrin.esa.it>
Cc: XEmacs Beta <xemacs-beta@xemacs.org>
Subject: Re: XEmacs-20.1-b3 is released
References: <9702271504.AA07869@mail.esrin.esa.it>
Mime-Version: 1.0 (generated by tm-edit 7.105)
Content-Type: text/plain; charset=US-ASCII
From: Neal Becker <neal@ctd.comsat.com>
Date: 27 Feb 1997 11:02:02 -0500
In-Reply-To: Simon Marshall's message of Thu, 27 Feb 97 15:04:48 GMT
Message-ID: <u9u3myqltx.fsf@neal.ctd.comsat.com>
Lines: 18
X-Mailer: Gnus v5.4.15/XEmacs 20.1

>>>>> "Simon" == Simon Marshall <Simon.Marshall@esrin.esa.it> writes:

    SB> (Please) No more complaints about lazy(good-for-nothing)-lock.el.
    SB> Either don't use it, or let's reach a consensus on which version
    SB> should be used.

    Simon> I assume you're talking about what version of lazy-lock.el version 1 to
    Simon> use, following the 2 problems that started with b95.

    Simon> 1.  Process output hang is the sit-for on post-command-hook XEmacs bug.
    Simon> This effects any lazy-lock.el version 1, at least if you have Lazy Lock
    Simon> mode on anywhere and have stealth enabled.  So it effects b95 with
    Simon> lazy-lock.el 1.14 + Ben hacks (from XEmacs 19.14), 1.15 and 1.16.  I just
    Simon> tested this with XEmacs 19.15b95 to confirm it.

This is NOT what I see with 20.1.  Process output is hanging, I didn't
track down why.  It ALWAYS happens with 1.16, and NOT with 1.15.  This
is true of 20.1b2, and 20.1b3.

