From: martin rudalics <rudalics@gmx.at>
To: 陈宇迪 <jodieydchen@gmail.com>
Cc: Po Lu <luangruo@yahoo.com>,
65183@debbugs.gnu.org, Eli Zaretskii <eliz@gnu.org>
Subject: bug#65183: 29.1; Child frame moving and resizing problems
Date: Tue, 15 Aug 2023 08:38:36 +0200 [thread overview]
Message-ID: <081d7b2c-3b37-03ac-ef43-2bc431261521@gmx.at> (raw)
In-Reply-To: <CACuMiX5YffmXmPqEiLNhQyEB+=27nCFvGdvg_D5bHKAV=V-1Rw@mail.gmail.com>
> Since I'm not familiar with Emacs' source code and the ideas, I find it
> difficult
> to write the patch code that has fewer duplicates, covers all corner cases,
> and is easy to maintain. So, I decided not to write this code.
That's a pity. From what you wrote so far I was convinced that you had
already covered everything needed.
> But I'm sure the resize and move functions can solve the issue that I
> mentioned
> in my first email, based on my tests.
>
> By the way, I suggest naming the function to add as
> `set-frame-position-and-size'
> instead of `set-frame-size-and-position', because most underlying APIs are
> called
> xxx_move_resize_xxx: `gdk_window_move_resize' (GTK), `XMoveResizeWindow'
> (X11),
> `MoveWindow(hWnd, X, Y, nWidth, nHeight, bRepaint)' (Windows).
I'll look into it when I have time.
Thanks, martin
prev parent reply other threads:[~2023-08-15 6:38 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
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 [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=081d7b2c-3b37-03ac-ef43-2bc431261521@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).