Subject: (fwd) Re: [[email-masked]: bug in lazy-lock step by step]

From: [email-masked] (Dan Nicolaescu)
Date: Fri, 30 Aug 1996 11:50:12 +0300 (BST)

Forwarded message:
>From [email-masked] Thu Aug 29 16:09:50 1996
Date: Thu, 29 Aug 1996 15:52:56 +0200 (IST)
From: Eli Zaretskii <[email-masked]>
To: Dan Nicolaescu <[email-masked]>
Cc: Simon Marshall <[email-masked]>
Subject: Re: [[email-masked]: bug in lazy-lock step by step]

> emacs -no-init-file -no-site-file
> (setq font-lock-support-mode 'lazy-lock-mode) C-j
>  ... seems that again by default *scratch* buffer is in lisp interaction mode
> C-x C-f c:/tools/emacs.95/lisp/cc-mode.el RET
> M-x font-lock-mode RET
>
> Wait for some time and when the message %s appears in the minibuffer:
> Fontifyng stealthly ... %xx of cc-mode.el
>
> Now if you click on the menubar the menu appears, but diappears very fast
> while lazy-lock is NOT interupted.
>
> Today I've upgraded so:
> M-: (emacs-version) RET
> "GNU Emacs 19.34.1 (i386-*-win954.0) of Tue Aug 27 1996 on DONE"

Emacs compiled for MSDOS doesn't behave that way, neither on MSDOS, nor
on Windows 3.x and Windows 95.  But `emacs-version' above says this is
Emacs compiled as native Win32 app for Windows 95, and I don't use that
port.  Please write to Geoff Voelker <[email-masked]> who
maintains the Win32 version and ask him to check this out.

Also, please make sure you don't have an old lazy-lock.elc somewhere on
your LOADPATH.  `lazy-lock' is now part of the official Emacs
distribution, but if you used it with previous Emacs versions, you might
be using an old (and incompatible) version of `lazy-lock'.