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 #111 received at 46827 <at> debbugs.gnu.org (full text, mbox):

From: Juri Linkov <juri <at> linkov.net>
To: martin rudalics <rudalics <at> gmx.at>
Cc: 46827 <at> debbugs.gnu.org
Subject: Re: bug#46827: Broken initial size of GTK3 frame
Date: Thu, 29 Apr 2021 19:13:30 +0300
> It's due to to the fact that WM notifications about new frame sizes may
> be processed earlier or later.  I tried to fix that behavior in commit
> a190b4cfd8b6f42a91678ac7292e1cceccd168e7 by having adjust_frame_size
> pick up such notifications on the fly and am closing this bug.

Unfortunately, this commit caused a regression: now there is distracting
blinking of the frame that looks like the visual effect of visible-bell
when it flashes the frame to represent a bell.

This problem can be reproduced only in Gnus.  With such configuration:

  (push '("\\`\\*Summary .*\\*\\'" .
          (display-buffer-in-tab
           (tab-name . "*Summary*")))
        display-buffer-alist)

opening a Gnus group in a new tab flashes the whole frame where empty space
instead of the frame content is visible for a short time.

This problem can't be reproduced with just creating a new tab,
it only manifests in Gnus, maybe something in gnus-summary-read-group-1
with gnus-configure-windows forces frame redisplay or something like this.

This problem doesn't exist without recent changes in a190b4cfd8.




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.