unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: martin rudalics <rudalics@gmx.at>
To: Eli Zaretskii <eliz@gnu.org>, "J. Scott Berg" <jsberg-bnl@outlook.com>
Cc: 44002@debbugs.gnu.org
Subject: bug#44002: 27.1; Small window height with VcXsrv X server when built with gtk3 toolkit
Date: Sat, 17 Oct 2020 11:32:39 +0200	[thread overview]
Message-ID: <9ad655db-7735-fb80-4517-3e3aaec13ee1@gmx.at> (raw)
In-Reply-To: <83y2k5thky.fsf@gnu.org>

 >> I did a bit more debugging. What seems to be happening is that we
 >> receive a pair of ConfigureNotify events in rapid succession. The
 >> first is for the top level window, and has a reasonable width and
 >> height. The second is for the window associated with the frame, but
 >> it has a width=1 height=1. This then leads to the resizing of the
 >> frame. Presumably the frame's window is not yet mapped, and thus the
 >> bogus width and height. Checking for visibility on the frame fixes
 >> the problem. I've attached a patch that works for me, but I haven't
 >> exhaustively tested all the various possible cases.
 >
 >
 > Martin, any comments on the proposed patch?  Or on the problem in
 > general?

I applied it here and didn't see any detrimental effects.  I suppose we
should just install it and look whether it causes problems with any of
our window managers.

For me the most interesting aspect is that it apparently works with
GTK2.  Maybe comparing the traces of GTK2 and GTK3 runs could reveal
more.  Or comparing a GTK3 trace with that of a Lucid build.

 > Btw, do we understand why this happens only with VcXsrv?

I never used VcXsrv so I don't know how it works.  As an example, I have
no idea what the "top level window" is and why it is not the same as the
"window associated with the frame".  Also, the fact that a "bogus
height" is propagated while a "bogus width" is not, hints at yet another
unresolved mystery.

martin





  reply	other threads:[~2020-10-17  9:32 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-15  1:55 bug#44002: 27.1; Small window height with VcXsrv X server when built with gtk3 toolkit J. Scott Berg
2020-10-16  7:31 ` Eli Zaretskii
2020-10-16 14:47   ` J. Scott Berg
2020-10-16 19:08     ` Eli Zaretskii
2020-10-16 19:47       ` J. Scott Berg
2020-10-16 23:29         ` J. Scott Berg
2020-10-17  7:52           ` Eli Zaretskii
2020-10-17  9:32             ` martin rudalics [this message]
2020-10-17  9:34               ` Eli Zaretskii
2020-10-17  9:40                 ` martin rudalics
2020-10-17 17:32                   ` Eli Zaretskii
2020-10-18 17:52                     ` Robert Pluim
2020-10-18 17:56                       ` Eli Zaretskii
2020-10-19  8:15                         ` Robert Pluim
2021-02-25 20:04                   ` Glenn Morris
2021-02-25 20:28                     ` J. Scott Berg
2021-02-25 20:38                     ` Eli Zaretskii
2020-10-19 14:02               ` J. Scott Berg

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=9ad655db-7735-fb80-4517-3e3aaec13ee1@gmx.at \
    --to=rudalics@gmx.at \
    --cc=44002@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=jsberg-bnl@outlook.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).