From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Jean Louis <bugs@gnu.support>
Cc: Stefan Kangas <stefankangas@gmail.com>, 58268@debbugs.gnu.org
Subject: bug#58268: 29.0.50; message-box appearing in center of other X window
Date: Thu, 06 Oct 2022 18:39:57 +0800 [thread overview]
Message-ID: <8735c1s0aq.fsf@yahoo.com> (raw)
In-Reply-To: <Yz6lDs4gZ5WBryMV@protected.localdomain> (Jean Louis's message of "Thu, 6 Oct 2022 12:51:10 +0300")
Jean Louis <bugs@gnu.support> writes:
> * Stefan Kangas <stefankangas@gmail.com> [2022-10-06 01:36]:
>> Jean Louis <bugs@gnu.support> writes:
>>
>> > I will not change to other toolkit.
>> >
>> > I did try that, but I will not change to that toolkit because of
>> > message-box appearing in other window.
>>
>> The request was not for you to change toolkit, but for you to *test*
>> with another toolkit, to see if the problem remains.
>>
>> Would you be willing to carry out such a test and report back the
>> results (in particular, if the problem remains)?
>
> Here is the video with 2 toolkits:
>
> https://gnu.support/images/tmp/2022-10-06/2022-10-06-10:54:20.ogv
>
> It takes place when I press ALT-SHIFT-F2 to tile windows.
Thanks.
In the case of GTK+, the toolkit itself sets the appropriate hints and
waits for the window manager to position the popup correctly. There is
nothing we can do about that.
Athena widgets (all kinds) on the other hand fail to set any hints at
all. I will look into this.
prev parent reply other threads:[~2022-10-06 10:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-03 6:24 bug#58268: 29.0.50; message-box appearing in center of other X window Jean Louis
2022-10-03 12:34 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-05 18:54 ` Jean Louis
2022-10-05 22:35 ` Stefan Kangas
2022-10-06 9:51 ` Jean Louis
2022-10-06 10:39 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
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=8735c1s0aq.fsf@yahoo.com \
--to=bug-gnu-emacs@gnu.org \
--cc=58268@debbugs.gnu.org \
--cc=bugs@gnu.support \
--cc=luangruo@yahoo.com \
--cc=stefankangas@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).