From xemacs-m  Thu Feb 27 08:15:53 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 IAA01529
	for <xemacs-beta@xemacs.org>; Thu, 27 Feb 1997 08:15:52 -0600 (CST)
Received: from neal by neal.ctd.comsat.com with local (Exim 1.58 #2)
	id 0w06ci-00023A-00; Thu, 27 Feb 1997 09:15:52 -0500
From: Neal Becker <neal@ctd.comsat.com>
To: xemacs-beta@xemacs.org
Subject: 20.1b3 lazy lock problems!
X-Face: "$ryF/ne$oms9n}#TY|W5Ttjbp-6/u4j'7c:%-aq2IAf'&DjuvII4wvr:eU{h=GMPcVTP,p
 XgCPnk{Qu:7P=jH00Q?B(*bZ\7#x_&KD=%hU1VhP'`hy'PF01*tU9DAoK7QXTGzL%fe!lIj,0Ds,P:
 GV_YPd*4GO?ClJAPRa=iB\PuIQmM=Q>qo87lJh-N2PQL-2QaM>}LdWI<}
Mime-Version: 1.0 (generated by tm-edit 7.105)
Content-Type: text/plain; charset=US-ASCII
Message-Id: <E0w06ci-00023A-00@neal.ctd.comsat.com>
Date: Thu, 27 Feb 1997 09:15:52 -0500

Are you surprised?  Same as 20.1b2.  The instant I do M-x load
lazy-lock, output from shellmode stops.  xemacs displays busy cursor
for a very very long time whenever I hit return.  I had to back down
to lazy-lock from 20.0.

Also, Signaling: (error "invalid lazy-loaded byte code" ble)
  turn-on-lazy-lock()
  run-hooks(font-lock-mode-hook)
  font-lock-mode(1)
  turn-on-font-lock()
  message-xmas-maybe-fontify()
  run-hooks(text-mode-hook message-mode-hook)
  message-mode()
  message-pop-to-buffer("*news*")
  message-news("")
  gnus-post-news(post "")
  gnus-group-post-news(nil)
  call-interactively(gnus-group-post-news)

