From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 65840@debbugs.gnu.org, tanzer@gg32.com
Subject: bug#65840: 29.1; desktop-load moves frames to the right and down
Date: Sat, 09 Sep 2023 21:35:01 +0800 [thread overview]
Message-ID: <871qf7cvwa.fsf@yahoo.com> (raw)
In-Reply-To: <83v8cjtscl.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 09 Sep 2023 15:59:38 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
> You are aware, I hope, that on X and similar GUI systems, the
> coordinates of the frames we request from the window-manager are
> advisory: the WM doesn't have to adhere to what we request. I'm not
> sure what you see is not a manifestation of that.
>
> Po Lu, can you chime in, please?
Thanks, but I'm not well versed in Mac OS window management. I would
begin an investigation into this behavior by calling:
(set-frame-position f 10 10)
waiting for a MOVE_FRAME_EVENT to arrive:
emacsframe->left_pos = (NSMinX (r)
- NS_PARENT_WINDOW_LEFT_POS (emacsframe));
emacsframe->top_pos = (NS_PARENT_WINDOW_TOP_POS (emacsframe)
- NSMaxY (r));
and attempting to establish which factors influence both the position
set by ns_set_offset and that returned within the consequent
MOVE_FRAME_EVENT. With that information at hand, it should become
possible to then devise a method of compensating for such factors, so as
to guarantee that the frame position through `set-frame-position' is
reflected faithfully within the frame's `left' and `top' properties,
insofar as the window manager elects to respect said position.
next prev parent reply other threads:[~2023-09-09 13:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-09 12:32 bug#65840: 29.1; desktop-load moves frames to the right and down tanzer--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-09 12:59 ` Eli Zaretskii
2023-09-09 13:35 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
[not found] ` <031260D8-4159-4BBC-A25F-A8BCBD88B7BA@gg32.com>
2023-09-09 14:47 ` Eli Zaretskii
2023-09-13 5:09 ` Gerd Möllmann
2023-09-13 5:48 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-13 18:04 ` Christian Tanzer via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-13 18:27 ` Christian Tanzer via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-13 18:51 ` Gerd Möllmann
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=871qf7cvwa.fsf@yahoo.com \
--to=bug-gnu-emacs@gnu.org \
--cc=65840@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=luangruo@yahoo.com \
--cc=tanzer@gg32.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).