From: drshapeless via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Po Lu <luangruo@yahoo.com>
Cc: 55779@debbugs.gnu.org
Subject: bug#55779: 29.0.50; child frame
Date: Sat, 04 Jun 2022 11:10:14 +0800 [thread overview]
Message-ID: <m24k11f7jd.fsf@drshapeless.com> (raw)
In-Reply-To: <87wndybdo1.fsf@drshapeless.com>
Po Lu <luangruo@yahoo.com> writes:
> drshapeless <drsl@drshapeless.com> writes:
>
>> I have commented out 2 calls in xfns.c and 1 call in xterm.c. But the
>> issue persists. A bit more detailed observation is that, the size of the
>> blocking overlay (just call it overlay now) is related to the last
>> completion child frame.
>>
>> For example, if the last child frame was 3-line tall, if the next child
>> frame is 5-line tall, only the first 3 lines are blocked.
>>
>> And still, this behaviour cannot be observed other than building with
>> gtk.
>
> I'm lost. What happens if you set `x-gtk-resize-child-frames' to
> `hide'?
I have tried this one even before sending the bug report, did not
help. The bug should be something related to gtk related commit in
master but not in 28.1 release. But I could not located it.
next prev parent reply other threads:[~2022-06-04 3:10 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 [this message]
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
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=m24k11f7jd.fsf@drshapeless.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).