From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Robert Pluim <rpluim@gmail.com>
Cc: martin rudalics <rudalics@gmx.at>,
Jimmy Yuen Ho Wong <wyuenho@gmail.com>,
74074@debbugs.gnu.org
Subject: bug#74074: 30.0.92; [NS] Frame position not reported on resize from top left
Date: Wed, 06 Nov 2024 20:52:05 +0800 [thread overview]
Message-ID: <87fro4iky2.fsf@yahoo.com> (raw)
In-Reply-To: <87ttckmzur.fsf@gmail.com> (Robert Pluim's message of "Wed, 06 Nov 2024 11:16:28 +0100")
Robert Pluim <rpluim@gmail.com> writes:
>>>>>> On Wed, 6 Nov 2024 10:31:12 +0100, martin rudalics <rudalics@gmx.at> said:
>
> >> I see that under X11, the `move-frame-functions' are called when
> >> resizing from the top left. I donʼt know what happens on MSWindows or
> >> in a pgtk build.
>
> martin> It works on MSWindows here. IIRC pgtk doesn't care abut positions at
> martin> all.
>
> pgtk doesnʼt let you programatically change the frame positions, but
> Iʼm assuming it still reports them <time passes> Hmm, no, it
> doesnʼt. I donʼt know if thatʼs expected or not. Po Lu?
It's expected, inasmuch as there are just no window positions under
Wayland. Where or how to position a toplevel surface visually is
compositor policy that is not exposed to clients.
next prev parent reply other threads:[~2024-11-06 12:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-28 23:36 bug#74074: 30.0.92; [NS] Frame position not reported on resize from top left Jimmy Yuen Ho Wong
2024-11-06 8:29 ` Robert Pluim
2024-11-06 9:31 ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-06 10:16 ` Robert Pluim
2024-11-06 12:52 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2024-11-06 12:58 ` Eli Zaretskii
2024-11-06 13:50 ` Robert Pluim
2024-11-06 13:59 ` Jimmy Wong
2024-11-06 14:36 ` Eli Zaretskii
2024-11-07 8:34 ` Robert Pluim
2024-11-07 18:26 ` Jimmy Wong
2024-11-07 20:13 ` Robert Pluim
2024-11-08 12:26 ` Jimmy Wong
2024-11-08 13:37 ` Robert Pluim
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87fro4iky2.fsf@yahoo.com \
--to=bug-gnu-emacs@gnu.org \
--cc=74074@debbugs.gnu.org \
--cc=luangruo@yahoo.com \
--cc=rpluim@gmail.com \
--cc=rudalics@gmx.at \
--cc=wyuenho@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.