From: drshapeless via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: drshapeless <drsl@drshapeless.com>
Subject: bug#55779: Acknowledgement (29.0.50; child frame)
Date: Fri, 03 Jun 2022 08:19:03 +0000 [thread overview]
Message-ID: <878rqevt8p.fsf@drshapeless.com> (raw)
In-Reply-To: <87wndybdo1.fsf@drshapeless.com>
Thank you for filing a new bug report with debbugs.gnu.org.
This is an automatically generated reply to let you know your message
has been received.
Your message is being forwarded to the package maintainers and other
interested parties for their attention; they will reply in due course.
Your message has been sent to the package maintainer(s):
bug-gnu-emacs@gnu.org
If you wish to submit further information on this problem, please
send it to 55779@debbugs.gnu.org.
Please do not send mail to help-debbugs@gnu.org unless you wish
to report a problem with the Bug-tracking system.
[ 4-line signature. Click/Enter to show. ]
--
55779: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=55779
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems
Po Lu <luangruo@yahoo.com> (Today 18:27) (replied)
Subject: Re: bug#55779: 29.0.50; child frame
To: drshapeless <drsl@drshapeless.com>
Cc: 55779@debbugs.gnu.org
Date: Fri, 03 Jun 2022 18:27:18 +0800
drshapeless <drsl@drshapeless.com> writes:
> When I build emacs --with-x-toolkit=gtk3, the child frame generated by
> corfu completion candidates are blocked by a blank overlay. I can
[ 7 more citation lines. Click/Enter to show. ]
> confirm this is only a gtk3 related issue, because I have built emacs
> --with-x-toolkit=athena or --with-x-toolkit=no without facing the same
> issue. Also, this issue does not occur on older stable branch,
> e.g. 28.1, I can still use gtk3 as the toolkit on older build without
> any issues.
>
> I have reached out to the author of corfu mode. The author says he
> cannot do anything because it is an issue related to emacs child frame
> mechanism. And my experiments on different build configurations showed
> the same conclusion.
What does "are blocked by a blank overlay" mean? It is technically
impossible for anything (such as an overlay) in the parent frame to
obscure the contents of the child frame, so I'm afraid I don't
understand what you mean by "blocked"?
Secondly, what happens if you start Emacs with
"GDK_CORE_DEVICE_EVENTS=1" in the environment?
Thanks.
drshapeless <drsl@drshapeless.com> (0 mins. ago) (sent)
Subject: Re: bug#55779: 29.0.50; child frame
To: Po Lu <luangruo@yahoo.com>
Date: Fri, 03 Jun 2022 20:11:43 +0800
Po Lu <luangruo@yahoo.com> writes:
> drshapeless <drsl@drshapeless.com> writes:
>> When I build emacs --with-x-toolkit=gtk3, the child frame generated by
[ 18 more citation lines. Click/Enter to show. ]
>> corfu completion candidates are blocked by a blank overlay. I can
>> confirm this is only a gtk3 related issue, because I have built emacs
>> --with-x-toolkit=athena or --with-x-toolkit=no without facing the same
>> issue. Also, this issue does not occur on older stable branch,
>> e.g. 28.1, I can still use gtk3 as the toolkit on older build without
>> any issues.
>>
>> I have reached out to the author of corfu mode. The author says he
>> cannot do anything because it is an issue related to emacs child frame
>> mechanism. And my experiments on different build configurations showed
>> the same conclusion.
>
> What does "are blocked by a blank overlay" mean? It is technically
> impossible for anything (such as an overlay) in the parent frame to
> obscure the contents of the child frame, so I'm afraid I don't
> understand what you mean by "blocked"?
>
> Secondly, what happens if you start Emacs with
> "GDK_CORE_DEVICE_EVENTS=1" in the environment?
>
> Thanks.
I just tried starting Emacs with "GDK_CORE_DEVICE_EVENTS=1", the only
difference is the smooth scrolling is gone. The child frame issue still
persists.
To be clear, it was said to be a child frame redisplay bug, (by
minad). It was not the parent frame blocking the child frame, instead it
seems to be another child frame blocking the child frame.
You may check out the github issue below, where I posted a couple photos
showing the bug.
https://github.com/minad/corfu/issues/161
next prev parent reply other threads:[~2022-06-03 8:19 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 ` drshapeless via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-06-03 10:27 ` 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
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=878rqevt8p.fsf@drshapeless.com \
--to=bug-gnu-emacs@gnu.org \
--cc=drsl@drshapeless.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).