From owner-ntemacs-users@cs.washington.edu  Fri Oct  2 12:46:15 1998
X-VM-v5-Data: ([nil nil nil nil t nil nil nil nil]
	[nil "Fri" " 2" "October" "1998" "15:16:28" "-0400" "Jim Corwin" "corwin@matrix-one.com" "<199810021916.PAA00750@matrixmail>" "23" "More problems with lazy-lock" "^From:" nil nil "10" 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.8.7+CS/7.2ju) with SMTP id MAA10863 for <voelker@june.cs.washington.edu>; Fri, 2 Oct 1998 12:46:14 -0700
Received: from trout.cs.washington.edu (trout.cs.washington.edu [128.95.1.178]) by joker.cs.washington.edu (8.6.12/7.2ws+) with ESMTP id MAA45911 for <voelker@joker.cs.washington.edu>; Fri, 2 Oct 1998 12:46:12 -0700
Received: (majordom@localhost) by trout.cs.washington.edu (8.8.5+CS/7.2ws+) id MAA13342 for ntemacs-users-outgoing; Fri, 2 Oct 1998 12:10:50 -0700 (PDT)
Received: from june.cs.washington.edu (june.cs.washington.edu [128.95.1.4]) by trout.cs.washington.edu (8.8.5+CS/7.2ws+) with ESMTP id MAA13338 for <ntemacs-users@trout.cs.washington.edu>; Fri, 2 Oct 1998 12:10:47 -0700 (PDT)
Received: from gateway-out (gateway2.matrix-one.com [208.196.3.98]) by june.cs.washington.edu (8.8.7+CS/7.2ju) with SMTP id MAA06094 for <ntemacs-users@cs.washington.edu>; Fri, 2 Oct 1998 12:10:45 -0700
Received: from [198.3.217.252] by gateway-out           via smtpd (for june.cs.washington.edu [128.95.2.4]) with SMTP; 2 Oct 1998 19:16:50 UT
Received: from TREGASTEL by matrixmail (SMI-8.6/SMI-SVR4) 	id PAA00750; Fri, 2 Oct 1998 15:16:28 -0400
Message-Id: <199810021916.PAA00750@matrixmail>
Precedence: bulk
X-FAQ: http://www.cs.washington.edu/homes/voelker/ntemacs.html
From: Jim Corwin <corwin@matrix-one.com>
Sender: owner-ntemacs-users@cs.washington.edu
To: ntemacs-users@cs.washington.edu
Subject: More problems with lazy-lock
Date: Fri, 2 Oct 1998 15:16:28 -0400

I perhaps spoke too soon when I said that my problems had been solved by
the fix from Simon Marshall.  That code fixed the problem caused by window-end.
However, I seem to have another one.  This time I have a problem with
lazy-lock-fontify-after-defer.

If I put lazy-lock.el in a window and run edebug-defun on this function,
after lazy-lock-defer-time I find myself entering the function.  So far so good.
The problem is with the variable lazy-lock-buffers.  This has one entry in it
for the lazy-lock window.  When I step through the code, I get to the line:
(setq lazy-lock-buffers (cdr lazy-lock-buffers))
This line sets lazy-lock-buffers to nil.  Great.  But when I continue stepping,
I come to the statement:
(while (and lazy-lock-buffers (not (input-pending-p))) and lo and behold
lazy-lock-buffers has been reset to its previous value.

I can not figure out why this is happening.  I tried setting breaks in each of
the functions capable of setting this variable.  When I set such a break in
lazy-lock-defer-after-scroll, I crash shortly thereafter.  So perhaps something
is wrong with that function.  I am not able to figure out more.

Someone please help.

Jim Corwin