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

Previous Next

Full log

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

From: "Dmitry Gutov" <dgutov <at> yandex.ru>
To: bug-gnu-emacs <at> gnu.org
Subject: Re: bug#61667: 29.0.60; Failure to redisplay
Date: Sun, 16 Apr 2023 20:46:39 +0300

[Message part 1 (text/plain, inline)]

On Sun, Apr 16, 2023, at 7:27 PM, Eli Zaretskii wrote:
> > Date: Sun, 16 Apr 2023 16:08:26 +0300
> > Cc: luangruo <at> yahoo.com, 61667 <at> debbugs.gnu.org, gregory <at> heytings.org
> > From: Dmitry Gutov <dgutov <at> yandex.ru>
> > 
> > 1. 'emacs -Q', disable stuff.
> > 2. 'C-x p f', visit lisp/emacs-lisp/smie.el.
> > 3. Search for something rare using 'C-x p g' (e.g. for "Coq-specific", 
> > but not necessarily).
> > 4. Press 'q' to exit the search.
> > 
> > On step 3 or 4, the title bar will get updated noticeably faster than 
> > the frame configuration changes.
> 
> When you say "gets updated noticeably faster", what exactly do you
> mean? by how much time does the redraw of the windows lag after the
> title bar update?
Can be on the order of seconds or indefinitely, just like described before.
> It is normal for the frame's title to be updated first, because Emacs
> redraws it early during a redisplay cycle. 
It's not usually noticeable with the naked eye.
> Only after that, the
> display engine examines all the windows and redraws whatever needs to
> be updated.  So it could take some short time between the two, perhaps
> more if the redisplay of windows requires to redraw a lot.  However,
> in your original message today you seemed to say that the windows are
> not updated unless you press something like C-n, and that should not
> happen.  Did I misunderstand your original report?
No, you got it right.

[Message part 2 (text/html, inline)]

Previous Next

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