From nexus.sorostm.ro!done@nexus.sorostm.ro Fri Aug 30 02:11:29 1996 X-VM-v5-Data: ([nil nil nil nil t nil nil nil nil] [nil "Fri" "30" "August" "1996" "11:58:59" "+0300" "Dan Nicolaescu" "done@nexus.sorostm.ro" "" "25" "the bug in lazy-lock" "^From:" nil nil "8" nil nil nil nil] nil) Received: from mailer.sorostm.ro ([193.226.98.3]) by june.cs.washington.edu (8.7.5/7.2ju) with SMTP id CAA29595 for ; Fri, 30 Aug 1996 02:11:18 -0700 Received: from nexus.UUCP (Unexus@localhost) by mailer.sorostm.ro (8.6.11/8.6.11) with UUCP id MAA15268 for voelker@cs.washington.edu; Fri, 30 Aug 1996 12:07:12 +0300 Received: by nexus.sorostm.ro (dMail for Windows v1.2b3, 29Mar96); Fri, 30 Aug 1996 11:58:59 +0300 Organization: softNRG Message-Id: X-Mailer: dMail [Demos Mail for Windows v1.2b3] Lines: 25 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: x-uuencode From: done@nexus.sorostm.ro (Dan Nicolaescu) To: voelker@cs.washington.edu Subject: the bug in lazy-lock Date: Fri, 30 Aug 1996 11:58:59 +0300 (BST) Hi Geoff! The previous message was forwarded to you after it has passed Simon Marshall (lazy-lock's author) (who couldn't reporduce it on X) and Eli Zaretskii who couldn't reproduce it in emacs compiled for MS-DOG. And they advised me to send the bug report to you. Can you reprpduce it, and discover where the problem is? If you need more details I can give you. Sometimes if you are realy fast and susced to select something from the menu before it dissapears emacs segfaults. No there is no other lazy-lock on my computer except the one from the 19.34's distribution. A similar problem with menus appears if you load flashparen.el ;; LCD Archive Entry: ;; flashparen|Noah Friedman|friedman@prep.ai.mit.edu| ;; flash matching parens a la Zmacs| ;; $Date: 1995/11/12 20:13:06 $|$Revision: 1.8 $|~/misc/flashparen.el.gz| and you try to select something from a menu while a paren is blinking. Thanks,Dan From nexus.sorostm.ro!done@nexus.sorostm.ro Fri Aug 30 02:12:02 1996 X-VM-v5-Data: ([nil nil nil nil nil nil nil nil nil] [nil "Fri" "30" "August" "1996" "11:50:12" "+0300" "Dan Nicolaescu" "done@nexus.sorostm.ro" nil "46" "(fwd) Re: [done@nexus.sorostm.ro: bug in lazy-lock step by step]" "^From:" nil nil "8" nil nil nil nil] nil) Received: from mailer.sorostm.ro (mailer.sorostm.ro [193.226.98.3]) by june.cs.washington.edu (8.7.5/7.2ju) with SMTP id CAA29635 for ; Fri, 30 Aug 1996 02:11:47 -0700 Received: from nexus.UUCP (Unexus@localhost) by mailer.sorostm.ro (8.6.11/8.6.11) with UUCP id MAA15267 for voelker@cs.washington.edu; Fri, 30 Aug 1996 12:07:12 +0300 Received: by nexus.sorostm.ro (dMail for Windows v1.2b3, 29Mar96); Fri, 30 Aug 1996 11:50:12 +0300 Organization: softNRG Message-Id: X-Mailer: dMail [Demos Mail for Windows v1.2b3] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit From: done@nexus.sorostm.ro (Dan Nicolaescu) To: voelker@cs.washington.edu Subject: (fwd) Re: [done@nexus.sorostm.ro: bug in lazy-lock step by step] Date: Fri, 30 Aug 1996 11:50:12 +0300 (BST) Forwarded message: >From mailer!eliz@is.elta.co.il Thu Aug 29 16:09:50 1996 Received: by nexus.sorostm.ro (dMail for Windows v1.2b3, 29Mar96); Thu, 29 Aug 1996 16:09:49 +0300 Received: (from root@localhost) by mailer.sorostm.ro (8.6.11/8.6.11) with UUCP id PAA07446 for done@nexus.sorostm.ro; Thu, 29 Aug 1996 15:55:06 +0300 Received: from is.elta.co.il (is.elta.co.il [199.203.121.2]) by cccsat.sorostm.ro (8.6.11/8.6.11) with SMTP id PAA32256 for ; Thu, 29 Aug 1996 15:53:23 +0300 Received: by is.elta.co.il (5.x/SMI-SVR4) id AA16811; Thu, 29 Aug 1996 15:52:57 +0200 Date: Thu, 29 Aug 1996 15:52:56 +0200 (IST) From: Eli Zaretskii X-Sender: eliz@is To: Dan Nicolaescu Cc: Simon Marshall Subject: Re: [done@nexus.sorostm.ro: bug in lazy-lock step by step] In-Reply-To: <9608271150.AA08248@mail.esrin.esa.it> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII > 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 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'. From owner-ntemacs-users@june Sun Aug 11 11:21:02 1996 X-VM-v5-Data: ([nil nil nil nil nil nil nil nil nil] [nil "Sun" "11" "August" "1996" "12:27:22" "-0400" "Randy Broussard" "rbroussa@afit.af.mil" nil "23" "19.32 and Lazy-Lock causes system crash in Win95" "^From:" nil nil "8" nil nil nil nil] nil) Received: from joker.cs.washington.edu (joker.cs.washington.edu [128.95.1.42]) by june.cs.washington.edu (8.7.5/7.2ju) with SMTP id LAA14672 for ; Sun, 11 Aug 1996 11:21:02 -0700 Received: from june.cs.washington.edu (june.cs.washington.edu [128.95.1.4]) by joker.cs.washington.edu (8.6.12/7.2ws+) with ESMTP id LAA40344 for ; Sun, 11 Aug 1996 11:21:01 -0700 Received: from stealth.afit.af.mil ([129.92.2.1]) by june.cs.washington.edu (8.7.5/7.2ju) with ESMTP id JAA08266 for ; Sun, 11 Aug 1996 09:28:30 -0700 Received: from rbroussa.erinet.com (dlp16.dayton.eri.net [207.0.229.46]) by stealth.afit.af.mil (8.7.5/8.7.3) with SMTP id MAA24140 for ; Sun, 11 Aug 1996 12:28:21 -0400 (EDT) Message-Id: <1.5.4.32.19960811162722.0066dab4@stealth.afit.af.mil> X-Sender: rbroussa@stealth.afit.af.mil X-Mailer: Windows Eudora Light Version 1.5.4 (32) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" From: Randy Broussard To: ntemacs-users@cs.washington.edu Subject: 19.32 and Lazy-Lock causes system crash in Win95 Date: Sun, 11 Aug 1996 12:27:22 -0400 When Lazy-Lock attempts stealthy fontification on a buffer while a NTEMACS window is pulled down and the cursor is over it, an unrecoverable system crash occurs in Win95. I'm running the 19.32 binary downloaded from the NTEMACS web page. The font-lock related lines in my _EMACS are (setq font-lock-support-mode 'lazy-lock-mode) (global-font-lock-mode t) (setq font-lock-face-attributes '((font-lock-comment-face "blue") (font-lock-string-face "ForestGreen") (font-lock-keyword-face "Aquamarine") (font-lock-function-name-face "OrangeRed") (font-lock-variable-name-face "Grey") (font-lock-type-face "dark red") (font-lock-reference-face "SpringGreen") (font-lock-maximum-decoration t))) Commenting out the lazy-lock-mode line removes the problem. Randy Broussard email: rbroussa@afit.af.mil