GNU bug report logs - #61667
29.0.60; Failure to redisplay

Previous Next

Full log

View this message in rfc822 format

From: Dmitry Gutov <dgutov <at> yandex.ru>
To: Eli Zaretskii <eliz <at> gnu.org>, Po Lu <luangruo <at> yahoo.com>
Cc: 61667 <at> debbugs.gnu.org, gregory <at> heytings.org
Subject: bug#61667: 29.0.60; Failure to redisplay
Date: Fri, 3 Mar 2023 15:06:11 +0200

On 03/03/2023 09:29, Eli Zaretskii wrote:
>> From: Po Lu <luangruo <at> yahoo.com>
>> Cc: Gregory Heytings <gregory <at> heytings.org>,  61667 <at> debbugs.gnu.org,  Eli
>>   Zaretskii <eliz <at> gnu.org>
>> Date: Fri, 03 Mar 2023 08:54:43 +0800
>>
>> Also, since we now know blink-cursor-mode was previously screwing with
>> the results, would you please try some other window manager again and
>> see if the problem reproduces without GNOME?
> 
> For a good measure, also disable global-eldoc-mode.  I've found long
> ago that blink-cursor-mode and global-eldoc-mode get in the way of
> debugging and testing various redisplay problems, because they tend to
> trigger extra redisplay cycles.
> 
> For an even cleaner environment, I suggest to disable all the timers
> that we run by default (see "M-x list-timers").  Timers change how our
> main loop behaves, and the routine redisplay calls are part of the
> main loop.
Thank you, I've added

  --eval "(global-eldoc-mode -1)" --eval "(show-paren-mode -1)" --eval 
"(cancel-timer show-paren--idle-timer)"

but that didn't seem to affect reproducibility, one way or the other.

This left just 2 timers in the list: undo--auto-boundary-timer, and 
another jit-lock related, both with intervals >0.5s.

Previous Next

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