GNU bug report logs - #56682
Fix the long lines font locking related slowdowns

Previous Next

Full log

Message #1859 received at 56682 <at> debbugs.gnu.org (full text, mbox):

From: Dmitry Gutov <dgutov <at> yandex.ru>
To: Gregory Heytings <gregory <at> heytings.org>, Eli Zaretskii <eliz <at> gnu.org>
Cc: 56682 <at> debbugs.gnu.org, Stefan Monnier <monnier <at> iro.umontreal.ca>
Subject: Re: bug#56682: locked narrowing
Date: Tue, 18 Oct 2022 19:30:05 +0300

(Sorry, resending after unarchiving the bug)

Hi Gregory,

I don't mean to hurry you up, but:

On 20.08.2022 19:20, Gregory Heytings wrote:
> 
> I pushed a (hopefully) improved version of the the locked narrowing 
> feature in the feature/improved-locked-narrowing branch.  It is now 
> possible:
> 
> 1. to unlock a locked narrowing,
> 
> 2. to use narrow-to-region and widen within the bounds of a locked 
> narrowing,
> 
> 3. to enter and leave a locked narrowing within a locked narrowing, and
> 
> 4. to use that feature in Lisp code (either directly or with a helper 
> macro).
> 
> As far as I understand, given that it is possible to unlock a locked 
> narrowing, adding the possibility to choose how the bounds of the locked 
> narrowings are computed has become unnecessary.

Does that mean that you concluded that font-lock will be able (and 
should) unlock the narrowing before doing its thing?

Which will be equivalent to not applying the narrowing in 
handle_fontified_prop to begin with.

Previous Next

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