GNU bug report logs - #56184
29.0.50; Increasing max-redisplay-ticks after it is set very low does nothing

Previous Next

Full log

Message #25 received at 56184-done <at> debbugs.gnu.org (full text, mbox):

From: Po Lu <luangruo <at> yahoo.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 56184-done <at> debbugs.gnu.org
Subject: Re: bug#56184: 29.0.50; Increasing max-redisplay-ticks after it is
 set very low does nothing
Date: Sat, 25 Jun 2022 08:02:51 +0800

Eli Zaretskii <eliz <at> gnu.org> writes:

>> From: Po Lu <luangruo <at> yahoo.com>
>> Cc: 56184 <at> debbugs.gnu.org
>> Date: Fri, 24 Jun 2022 21:08:15 +0800
>> 
>> Eli Zaretskii <eliz <at> gnu.org> writes:
>> 
>> > What do you expect it to do?
>> 
>> To redraw the entire frame, since max-redisplay-ticks is now
>> sufficiently large.
>
> That won't happen, unless you type C-l or make some change (e.g., type
> a character) into *scratch*, because the buffer *scratch* is marked
> "not to be redisplayed", and the only window on the frame is the
> window showing *scratch*.  So this is the expected and documented
> behavior.

Okay then, so I'm closing this bug.

Thanks.

Previous Next

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