From xemacs-m  Mon Jan  6 04:37:14 1997
Received: from dres.elam.org (dres@cola169.scsn.net [206.25.247.169])
          by xemacs.cs.uiuc.edu (8.8.4/8.8.4) with ESMTP
	  id EAA24843 for <xemacs-beta@xemacs.org>; Mon, 6 Jan 1997 04:37:11 -0600 (CST)
Received: (from dres@localhost) by dres.elam.org (8.7.6/8.7.3) id FAA06215; Mon, 6 Jan 1997 05:34:08 -0500
To: xemacs-beta@xemacs.org
Subject: Re: lazy lock
References: <199701060801.DAA02559@dres.elam.org>
	<rvohf3z0g4.fsf@sdnp5.ucsd.edu>
Mime-Version: 1.0 (generated by tm-edit 7.100)
Content-Type: text/plain; charset=US-ASCII
From: James LewisMoss <dres@dres.elam.org>
Date: 06 Jan 1997 05:34:07 -0500
In-Reply-To: David Moore's message of 06 Jan 1997 00:12:43 -0800
Message-ID: <hhbub3w0rk.fsf@dres.elam.org>
Lines: 58
X-Mailer: Gnus v5.2.40/XEmacs 20.0

>>>>> "David" == David Moore <dmoore@UCSD.EDU> writes:

 David> James LewisMoss <dres@dres.elam.org> writes:

 >> Had to turn off lazy lock to make gnus happy it was pausing
 >> anytime I tried to open an article or read a new group.  I saw
 >> similar bug report and just wanted to put in another 'I'm messed
 >> up' vote. :)

 David> 	I've heard people report that lazy-lock can sometimes
 David> interact badly with Gnus, modulo the recent lazy-lock patch.
 David> So, you might want to see if you still have problems with the
 David> patch applied.

After applying this patch everything seems happy with gnus again:
--- lazy-lock.el.orig	Sat Jan  4 18:05:14 1997
+++ lazy-lock.el	Sun Jan  5 16:56:59 1997
@@ -874,7 +874,9 @@
 ;; These fix bugs in `text-property-any' and `text-property-not-all'.  They may
 ;; not work perfectly in 19.11 and below because `next-single-property-change'
 ;; is also broke and not easily fixable in Lisp.
-(if (and lazy-lock-running-xemacs-p (< emacs-minor-version 12))
+(if (and lazy-lock-running-xemacs-p 
+	 (= emacs-major-version 19)
+	 (< emacs-minor-version 12))
     (progn
       ;; Loop through property changes until found.  This fix includes a work
       ;; around which prevents a bug in `window-start' causing a barf here.
@@ -904,7 +906,9 @@
 ;; than `face'.  Since `font-lock-unfontify-region' only removes `face', and we
 ;; have non-font-lock properties hanging about, `text-prop' never gets removed.
 ;; Unfortunately `font-lock-any-extents-p' is inlined so we can't redefine it.
-(if (and lazy-lock-running-xemacs-p (< emacs-minor-version 12))
+(if (and lazy-lock-running-xemacs-p 
+	 (= emacs-major-version 19)
+	 (< emacs-minor-version 12))
     (add-hook 'font-lock-mode-hook
      (function (lambda ()
 	(remove-hook 'after-change-functions 'font-lock-after-change-function)
@@ -921,7 +925,9 @@
 		;; Now set `fontified' to t to stop `lazy-lock-fontify-window'.
 		(put-text-property beg end 'fontified t))))))))))
 
-(if (and lazy-lock-running-xemacs-p (>= emacs-minor-version 12))
+(if (and lazy-lock-running-xemacs-p
+	 (or (> emacs-major-version 19)
+	     (>= emacs-minor-version 12)))
     ;; XEmacs 19.12 font-lock.el's `font-lock-fontify-buffer' runs a hook.
     (add-hook 'font-lock-after-fontify-buffer-hook
 	      'lazy-lock-after-fontify-buffer))

Jim
--
@James LewisMoss                 | moss@cs.sc.edu | Blessed Be!
@    http://www.cs.sc.edu/~moss  | dres@scsn.net  | Linux is cool!
@"Argue for your limitations and sure enough, they're yours." Bach


