From: Eli Zaretskii <eliz@gnu.org>
To: Po Lu <luangruo@yahoo.com>
Cc: 67654@debbugs.gnu.org, roshan.shariff@gmail.com
Subject: bug#67654: 29.1; Hiding menu bar makes new frames very small
Date: Mon, 11 Dec 2023 14:14:23 +0200 [thread overview]
Message-ID: <83msuhueao.fsf@gnu.org> (raw)
In-Reply-To: <87jzplkx4i.fsf@yahoo.com> (message from Po Lu on Mon, 11 Dec 2023 15:37:49 +0800)
> From: Po Lu <luangruo@yahoo.com>
> Cc: Eli Zaretskii <eliz@gnu.org>, 67654@debbugs.gnu.org
> Date: Mon, 11 Dec 2023 15:37:49 +0800
>
> Roshan Shariff <roshan.shariff@gmail.com> writes:
>
> > I tried a git bisect only to find that commits as far back as ~2015
> > exhibit the bug; I wasn't able to compile older versions on my system
> > because of segfaults during compilation. So it seems plausible that
> > the GTK3 build of Emacs has always had this issue.
>
> It's much more plausible that some change to GTK has introduced this
> bug... so much for breaking changes not being made to GTK 3.
Sounds like some GTK setting gets in the way and changes the
dimensions?
If the OP wanted to look deeper into this problem, would it be
possible to provide instructions where to look and which variables or
events to examine?
next prev parent reply other threads:[~2023-12-11 12:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAG8iPGxmb2f-1PH6HKEbLzchr+DRE2DAiCWG6YKmAOX6+ORdGA@mail.gmail.com>
2023-12-06 8:26 ` bug#67654: 29.1; Hiding menu bar makes new frames very small Roshan Shariff
2023-12-06 12:33 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-12-06 12:39 ` Eli Zaretskii
2023-12-06 16:48 ` Roshan Shariff
2023-12-11 7:13 ` Roshan Shariff
2023-12-11 7:37 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-12-11 12:14 ` Eli Zaretskii [this message]
2023-12-11 12:38 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-19 1:57 ` John Avery
2023-12-06 7:52 Roshan Shariff
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=83msuhueao.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=67654@debbugs.gnu.org \
--cc=luangruo@yahoo.com \
--cc=roshan.shariff@gmail.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).