From xemacs-m  Sun Jan  5 11:31:32 1997
Received: from mailhost.lanl.gov (mailhost.lanl.gov [128.165.3.12])
          by xemacs.cs.uiuc.edu (8.8.4/8.8.4) with ESMTP
	  id LAA11963 for <xemacs-beta@xemacs.org>; Sun, 5 Jan 1997 11:31:32 -0600 (CST)
Received: from xdiv.lanl.gov (xdiv.lanl.gov [128.165.116.106]) by mailhost.lanl.gov (8.8.4/8.8.3) with ESMTP id KAA05192 for <xemacs-beta@xemacs.org>; Sun, 5 Jan 1997 10:31:34 -0700 (MST)
Received: from branagh.lanl.gov (branagh.lanl.gov [128.165.16.72]) by xdiv.lanl.gov (8.6.12/8.6.12) with ESMTP id KAA08662 for <xemacs-beta@xemacs.org>; Sun, 5 Jan 1997 10:31:34 -0700
Received: by branagh.lanl.gov (SMI-8.6/SMI-SVR4)
	id KAA02964; Sun, 5 Jan 1997 10:29:00 -0700
Date: Sun, 5 Jan 1997 10:29:00 -0700
Message-Id: <199701051729.KAA02964@branagh.lanl.gov>
From: John Turner <turner@xdiv.lanl.gov>
To: xemacs-beta@xemacs.org
Subject: Re: Lazy lock broken in b34
In-Reply-To: <199701050718.CAA08228@spacely.icd.teradyne.com>
References: <199701050718.CAA08228@spacely.icd.teradyne.com>
Reply-To: turner@lanl.gov

Vinnie Shelton writes:

 > Lazy lock doesn't work at all in b34.  emacs seems to hang until you 
 > interrupt it with ^G.  Font-lock works by itself, tho.

Maybe a dumb question, but is it really hung or is this back to the
"waiting for some input" thing?  In other words, what happens if you
just do ^l?

-John

