From: martin rudalics <rudalics@gmx.at>
To: "Eli Zaretskii" <eliz@gnu.org>, 陈宇迪 <jodieydchen@gmail.com>,
"Po Lu" <luangruo@yahoo.com>
Cc: 65183@debbugs.gnu.org
Subject: bug#65183: 29.1; Child frame moving and resizing problems
Date: Fri, 11 Aug 2023 09:06:38 +0200 [thread overview]
Message-ID: <13c2f66e-861d-2ab3-6405-a2b57b29863b@gmx.at> (raw)
In-Reply-To: <837cq3jmyk.fsf@gnu.org>
>> 2. In the code I gave, `set-frame-size' should be executed before `set-frame-position'.
>> But in fact, the child frame was first moved, and then resized. It is in the wrong order.
>
> I don't think you can trust the order in this case, as at least some
> of the actual move/resize is performed by the window-manager.
... and Emacs only fills its text into the areas provided and exposed by
the window manager. As a rule, never trust the order of execution in
such case. Resizing child frames is already tricky enough with GTK3 and
some window managers. We have the variable 'x-gtk-resize-child-frames'
for that but setting it shouldn't change anything in the case at hand.
Neither should 'x-gtk-use-window-move' help but you can still try.
martin
next prev parent reply other threads:[~2023-08-11 7:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-09 14:28 bug#65183: 29.1; Child frame moving and resizing problems 陈宇迪
2023-08-10 8:55 ` Eli Zaretskii
[not found] ` <CACuMiX6AnPcrhPOni-jgr5NmJ9-qG5UXCE5cFB_vN8b2OLZcjQ@mail.gmail.com>
2023-08-10 17:31 ` Eli Zaretskii
2023-08-11 7:06 ` martin rudalics [this message]
2023-08-11 8:01 ` 陈宇迪
2023-08-11 10:00 ` martin rudalics
2023-08-11 16:09 ` 陈宇迪
2023-08-12 0:13 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-12 7:00 ` martin rudalics
2023-08-12 6:52 ` martin rudalics
2023-08-12 13:55 ` 陈宇迪
2023-08-13 7:21 ` martin rudalics
2023-08-13 13:34 ` 陈宇迪
2023-08-15 6:38 ` martin rudalics
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=13c2f66e-861d-2ab3-6405-a2b57b29863b@gmx.at \
--to=rudalics@gmx.at \
--cc=65183@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=jodieydchen@gmail.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).