GNU bug report logs - #57447
28.1.90; Can font-lock stop requesting fontification of invisible text?

Previous Next

Full log

View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Ihor Radchenko <yantar92 <at> gmail.com>, Stefan Monnier <monnier <at> iro.umontreal.ca>
Cc: 57447 <at> debbugs.gnu.org
Subject: bug#57447: 28.1.90; Can font-lock stop requesting fontification of invisible text?
Date: Sat, 27 Aug 2022 14:05:00 +0300

> From: Ihor Radchenko <yantar92 <at> gmail.com>
> Cc: 57447 <at> debbugs.gnu.org
> Date: Sat, 27 Aug 2022 18:37:36 +0800
> 
> > If the size is smaller than the visible portion of the buffer, it will
> > cause repeated calls to fontification-functions, instead of just one
> > call.  If fontification-functions do their job in approximately linear
> > time, you shouldn't see any adverse effects, I think.  But if each
> > call to fontification-functions incurs some one-time overhead that is
> > relatively expensive, the result could be slower redisplay when the
> > window is scrolled a lot.
> 
> This may be an issue in some scenarios.
> I am wondering if something like font-lock-extend-region-functions may
> be utilized to shrink the fontification boundaries.

I don't know.  Maybe Stefan does.

> > I only want to test that if you see something that is inconsistent
> > with my description of how this stuff works, including the value of
> > jit-lock-chunk-size.
> 
> If jit-lock-chunk-size must be an actual upper bound
>  "Jit-lock fontifies chunks of at most this many characters at a time."
> 
> then it does not always hold:

How did you collect the BEG and END values?  FWIW, I don't see
anything in jit-lock that enlarges the chunk size, except perhaps in
the stealth-fontification case, which you didn't activate?

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.