From xemacs-m  Tue Sep 16 07:10:50 1997
Received: from frege.math.ethz.ch (root@frege-d-math-north-g-west.math.ethz.ch [129.132.145.3])
	by xemacs.org (8.8.5/8.8.5) with SMTP id HAA04286
	for <xemacs-beta@xemacs.org>; Tue, 16 Sep 1997 07:10:49 -0500 (CDT)
Received: from midget (vroonhof@midget [129.132.145.4]) by frege.math.ethz.ch (8.6.12/Main-STAT-mailer) with ESMTP id OAA20782 for <xemacs-beta@xemacs.org>; Tue, 16 Sep 1997 14:10:51 +0200
Received: (vroonhof@localhost) by midget (SMI-8.6/D-MATH-client) id OAA17472; Tue, 16 Sep 1997 14:10:50 +0200
To: xemacs-beta@xemacs.org
Subject: Re: `lazyshot.el': bugfix and comments/questions.
References: <199709120745.AAA17290@bittersweet.inetarena.com> <bywwkm4wx3.fsf@midget.math.ethz.ch> <87d8md7kg6.fsf@bittersweet.inetarena.com>
Mime-Version: 1.0 (generated by tm-edit 7.106)
Content-Type: text/plain; charset=US-ASCII
From: Jan Vroonhof <vroonhof@math.ethz.ch>
Date: 16 Sep 1997 14:10:50 +0200
In-Reply-To: karlheg@inetarena.com's message of 13 Sep 1997 00:16:09 -0700
Message-ID: <by67s1mpbp.fsf@midget.math.ethz.ch>
Lines: 32
X-Mailer: Gnus v5.4.55/XEmacs 19.15

karlheg@inetarena.com (Karl M. Hegbloom) writes:

>     Jan> Thanks for checking this out. Do you notice any flashing?
> 
>  Not really... when the buffer first displays, it's black and white,
> and then it colorizes right away, just a snick slower than an
> eyeblink.

That's what I meant with flashing. It can only be solved by hacking
the C code to not to paint the uncolored regions. It is just the
question whether it is worth it.

>  I think it's great that lazy locking works so well now with such a
> minimal set of lisp functions.

That's what I thought too. (Although it'll probably increase again
when we add the timer stuff)

> >  I don't know where point is when I get to where start and end need to
> be calculated.  I can't see how forward-line would do what we want
> here.

The idea is to find the next line begin AFTER "end". Yours searches
the one "BEFORE" which one line too few.

>  ... so I guess fix the `extent-buffer'.  What was `font-lock-f' going
> to be for?

Not sure. Probably a pasto. Lazy-lock.el (v2) also sets some
"f-l-*-cache" to nil, I am not sure where that is for.

Jan

