From xemacs-m  Tue Feb 25 09:43:33 1997
Received: from maes.esrin.esa.it (maes.esrin.esa.it [192.106.252.50])
	by xemacs.org (8.8.5/8.8.5) with SMTP id JAA05336
	for <xemacs-beta@xemacs.org>; Tue, 25 Feb 1997 09:43:31 -0600 (CST)
Received: from mail.esrin.esa.it (plod.esrin.esa.it) by maes.esrin.esa.it with SMTP id AA16123
  (5.65c/IDA-1.4.4 for <xemacs-beta@xemacs.org>); Tue, 25 Feb 1997 16:43:32 +0100
Received: from penelope.esa.it by mail.esrin.esa.it (4.1/SMI-4.1)
	id AA17904; Tue, 25 Feb 97 15:43:34 GMT
Date: Tue, 25 Feb 97 15:43:34 GMT
Message-Id: <9702251543.AA17904@mail.esrin.esa.it>
Received: by penelope.esa.it (4.1/SMI-4.1)
	id AA14305; Tue, 25 Feb 97 16:48:16 +0100
From: Simon Marshall <Simon.Marshall@esrin.esa.it>
To: XEmacs Beta <xemacs-beta@xemacs.org>
In-Reply-To: <u9wwrxq70e.fsf@neal.ctd.comsat.com> (message from Neal Becker on
	25 Feb 1997 09:45:21 -0500)
Subject: Re: [19.15-b95 / 20.1-b2] lazy-lock lossage?
Reply-To: Simon Marshall <Simon.Marshall@esrin.esa.it>

Neal> Has nothing to do with it.  Once lazy-lock is loaded xemacs turns to
Neal> shit.

An easier way to screw things up is:

xemacs -no-init-file -no-site-file

(defun fubar ()
  (message "sit-for = %s" (sit-for 30)))

(add-hook 'post-command-hook 'fubar)

M-x eval-buffer RET RET M-x shell RET

