GNU bug report logs - #45898
27.1; wedged in redisplay again

Previous Next

Full log

View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Stefan Monnier <monnier <at> iro.umontreal.ca>
Cc: gerd.moellmann <at> gmail.com, psainty <at> orcon.net.nz, larsi <at> gnus.org, Emacs-hacker2018 <at> jovi.net, 45898 <at> debbugs.gnu.org
Subject: bug#45898: 27.1; wedged in redisplay again
Date: Fri, 01 Jul 2022 18:43:46 +0300

> From: Stefan Monnier <monnier <at> iro.umontreal.ca>
> Cc: gerd.moellmann <at> gmail.com,  larsi <at> gnus.org,  psainty <at> orcon.net.nz,
>   Emacs-hacker2018 <at> jovi.net,  45898 <at> debbugs.gnu.org
> Date: Fri, 01 Jul 2022 10:38:37 -0400
> 
> > In scan_sexps_forward, near the end: if too many "ticks" are counted,
> > update_redisplay_ticks will signal an error.  Same thing in
> > re_match_2_internal.
> 
> Ah... neat, thanks!
> Indeed, I can see the effect with:
> 
>     src/emacs -Q --eval '(setq syntax-wholeline-max most-positive-fixnum)' \
>                  --eval '(setq max-redisplay-ticks 100000)'                \
>                  ~/tmp/medium_line.json
> 
> in which case I get a warning about redisplay taking too long, whereas with:
> 
>     src/emacs -Q --eval '(setq max-redisplay-ticks 100000)' \
>                  ~/tmp/medium_line.json
> 
> I don't (because the `syntax-wholeline-max` keeps the font-lock time
> under control).

Good, so this change does have the expected effect.

Previous Next

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