GNU bug report logs - #57207
29.0.50; Fontification is slow after e7b5912b23 (Improvements to long lines handling)

Previous Next

Full log

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

From: Eli Zaretskii <eliz <at> gnu.org>
To: Gregory Heytings <gregory <at> heytings.org>
Cc: larsi <at> gnus.org, 57207 <at> debbugs.gnu.org, yantar92 <at> gmail.com
Subject: Re: bug#57207: 29.0.50; Fontification is slow after e7b5912b23
 (Improvements to long lines handling)
Date: Sun, 21 Aug 2022 16:39:52 +0300

> Date: Sun, 21 Aug 2022 13:32:16 +0000
> From: Gregory Heytings <gregory <at> heytings.org>
> cc: Eli Zaretskii <eliz <at> gnu.org>, 57207 <at> debbugs.gnu.org, yantar92 <at> gmail.com
> 
> 
> >
> > Here's a full test case.
> >
> 
> Thanks!
> 
> >
> > emacs -Q and then:
> >
> > (progn
> >  (pop-to-buffer "foo.txt")
> >  (flyspell-mode)
> >  (insert "\n\n"
> > 	  (propertize (make-string 20000 ?x) 'display "foo")
> > 	  "\n\nbar\nzot\n")
> >  (goto-char (point-min)))
> >
> > Then type `d'.  Everything after "foo" disappears.
> >
> 
> It doesn't, here :(  Strange...

It does here.

Btw, one more aspect of narrowing in safe_run_hooks_maybe_narrowed is
that the clip_changed flag of the current buffer is set, which means
any calls to 'redisplay' inside the hook will cause the display engine
to work harder.  If we temporarily restore the narrowing in
redisplay_internal, we may wish to undo that, but doing so will only
be possible if we save the original state of the flag, before
narrow-to-region inside safe_run_hooks_maybe_narrowed, in the
outermost-narrowing value, or something like that.

Previous Next

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