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

Previous Next

Full log

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

From: Eli Zaretskii <eliz <at> gnu.org>
To: Dmitry Gutov <dgutov <at> yandex.ru>
Cc: luangruo <at> yahoo.com, 61667 <at> debbugs.gnu.org, gregory <at> heytings.org
Subject: Re: bug#61667: 29.0.60; Failure to redisplay
Date: Sun, 16 Apr 2023 15:59:40 +0300

> Date: Sun, 16 Apr 2023 15:52:51 +0300
> Cc: luangruo <at> yahoo.com, 61667 <at> debbugs.gnu.org, gregory <at> heytings.org
> From: Dmitry Gutov <dgutov <at> yandex.ru>
> 
> On 16/04/2023 09:01, Eli Zaretskii wrote:
> >> Date: Sun, 16 Apr 2023 03:48:56 +0300
> >> From: Dmitry Gutov<dgutov <at> yandex.ru>
> >> Cc: Gregory Heytings<gregory <at> heytings.org>, Eli Zaretskii<eliz <at> gnu.org>,
> >>   Po Lu<luangruo <at> yahoo.com>
> >>
> >> - Do some search using 'C-x p g', wait to see the results buffer
> >> displayed but it's not displayed for a while. I look at the title bar -
> >> and it already says*xref*, but the frame is still not updated. If I
> >> press something like 'C-n' or 'C-f' now, that triggers the necessary
> >> refresh.
> >>
> >> - When the said Xref buffers is selected, I press 'q'. Likewise, the
> >> frame might not get updated for a while, still showing the previous
> >> window configuration until I issue the next command.
> >>
> >> These are of course random and don't happen every time. Often enough to
> >> be annoying, though.
> > Is this with or without double-buffering?  If it's with
> > double-buffering, do the problems go away if you disable
> > double-buffering?
> 
> Good question: the above failure scenario reproduces even without XDBE. 
> The frequency is about the same as with XDBE.

Thanks.  Next question: does it reproduce easily in "emacs -Q"?

Previous Next

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