From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: drshapeless <drsl@drshapeless.com>
Cc: 55779@debbugs.gnu.org
Subject: bug#55779: 29.0.50; child frame
Date: Sun, 05 Jun 2022 08:49:56 +0800 [thread overview]
Message-ID: <87ilpg0w97.fsf@yahoo.com> (raw)
In-Reply-To: <87o7z8wf5j.fsf@drshapeless.com> (drshapeless's message of "Sun, 05 Jun 2022 00:46:00 +0800")
drshapeless <drsl@drshapeless.com> writes:
> After a couple of hours, I am able to locate the bad commit using "git
> bisect". Here's the log. You probably made a change in GTK back in April
> leading to this bug.
Thanks, but that doesn't make much sense. Updating a window's opaque
region by calling its `style_changed' function shouldn't interfere with
updating it or changing its size.
What happens if you comment out this part out?
object_class = G_OBJECT_GET_CLASS (FRAME_GTK_OUTER_WIDGET (f));
class = GTK_WIDGET_CLASS (object_class);
if (class->style_updated)
class->style_updated (FRAME_GTK_OUTER_WIDGET (f));
Thanks.
next prev parent reply other threads:[~2022-06-05 0:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-03 3:59 bug#55779: 29.0.50; child frame drshapeless via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-03 8:19 ` bug#55779: Acknowledgement (29.0.50; child frame) drshapeless via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-03 10:27 ` bug#55779: 29.0.50; child frame Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
[not found] ` <87ee06vtds.fsf@drshapeless.com>
[not found] ` <87ee063piv.fsf@yahoo.com>
2022-06-03 14:56 ` drshapeless via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-04 1:15 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-04 3:10 ` drshapeless via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-04 4:18 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-04 11:57 ` drshapeless via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-04 12:09 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-04 16:46 ` drshapeless via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-05 0:49 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-06-05 1:03 ` drshapeless via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-05 2:54 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-05 3:55 ` drshapeless via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-05 5:04 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=87ilpg0w97.fsf@yahoo.com \
--to=bug-gnu-emacs@gnu.org \
--cc=55779@debbugs.gnu.org \
--cc=drsl@drshapeless.com \
--cc=luangruo@yahoo.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).