[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#45898: 27.1; wedged in redisplay again
From: |
Stefan Monnier |
Subject: |
bug#45898: 27.1; wedged in redisplay again |
Date: |
Fri, 01 Jul 2022 10:38:37 -0400 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) |
>> >> > That's only true if max-redisplay-ticks is zero.
>> >>
>> >> Why would that make a difference?
>> >
>> > Because if it is not zero, we won't let the entire line to be
>> > fontified, we will stop that before it gets to the end of the line.
>>
>> Interesting, where in the code do you do that?
>
> 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).
Stefan
- bug#45898: 27.1; wedged in redisplay again, (continued)
bug#45898: 27.1; wedged in redisplay again, Gerd Möllmann, 2022/07/01
bug#45898: 27.1; wedged in redisplay again, Eli Zaretskii, 2022/07/01
bug#45898: 27.1; wedged in redisplay again, Eli Zaretskii, 2022/07/01