GNU bug report logs - #46827
Broken initial size of GTK3 frame

Previous Next

Package: emacs;

Reported by: martin rudalics <rudalics <at> gmx.at>

Date: Sun, 28 Feb 2021 09:32:01 UTC

Severity: normal

Tags: fixed

Fixed in version 28.1

Done: martin rudalics <rudalics <at> gmx.at>

Bug is archived. No further changes may be made.

Full log


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

From: martin rudalics <rudalics <at> gmx.at>
To: Juri Linkov <juri <at> linkov.net>
Cc: 46827 <at> debbugs.gnu.org
Subject: Re: bug#46827: Broken initial size of GTK3 frame
Date: Fri, 30 Apr 2021 08:26:25 +0200
>> Please try to provide some sort of recipe to reproduce this.  Ideally
>> without Gnus because I never used it.  Also, I've never seen a frame
>
> Sorry, not easy to distill many different things Gnus does to massage windows
> into a simpler test case.

I understand.  But since nobody else has reported a similar issue till
now, I strongly suspect that `display-buffer-in-tab' is triggering it.

>> "flash".  Is that a new frame?  Is there anything broken in the frame
>> after the flash?
>
> It's in the same frame, and nothing is broken after the flash.
> The visual effect is that after creating a new tab, everything
> is erased on the frame including tab bars and the mode line
> for a short time, and then redrawn back.

If this is GTK can you try with `x-wait-for-event-timeout' set to say 10
and tell whether that "flash" then takes ten seconds?  Here I've never
seen that "everything is erased on the frame" - usually some garbage
from elsewhere remains ...

martin




This bug report was last modified 4 years and 11 days ago.

Previous Next


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