From: Lars Ingebrigtsen <larsi@gnus.org>
To: Po Lu <luangruo@yahoo.com>
Cc: James Ahlborn <jahlborn@getguru.com>,
martin rudalics <rudalics@gmx.at>,
54863@debbugs.gnu.org
Subject: bug#54863: 28.1; hook move-frame-functions not working in emacs 28.1
Date: Tue, 06 Sep 2022 15:40:05 +0200 [thread overview]
Message-ID: <8735d4sjt6.fsf@gnus.org> (raw)
In-Reply-To: <871qsobp7i.fsf@yahoo.com> (Po Lu's message of "Tue, 06 Sep 2022 21:35:29 +0800")
Po Lu <luangruo@yahoo.com> writes:
> Nice! Are the values of the parameters `left' and `top' correct too
> once the hook fires? Converting between the cartesian NS screen
> coordinate system and the X one is sometimes tricky, and I don't
> completely understand the NS_PARENT_WINDOW_XXX_POS macros.
Yes, it looks like they're correct. If I drag the frame as far left and
top as it gets, I get a left value of 0 and a top value of 25 -- but the
Macos menu bar is to the top. Eyeballing it by dragging it so that it
has a top value of 50, I then have a space of two menu bars above the
frame.
So looks correct to me.
next prev parent reply other threads:[~2022-09-06 13:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-11 20:18 bug#54863: 28.1; hook move-frame-functions not working in emacs 28.1 James Ahlborn via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-04-12 7:45 ` martin rudalics
2022-04-12 8:14 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-06 11:20 ` Lars Ingebrigtsen
2022-09-06 12:13 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-06 13:24 ` Lars Ingebrigtsen
2022-09-06 13:35 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-06 13:40 ` Lars Ingebrigtsen [this message]
2022-09-07 1:05 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-07 12:51 ` Lars Ingebrigtsen
2022-04-12 21:25 ` James Ahlborn via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-04-13 8:45 ` martin rudalics
2022-04-13 13:07 ` James Ahlborn via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=8735d4sjt6.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=54863@debbugs.gnu.org \
--cc=jahlborn@getguru.com \
--cc=luangruo@yahoo.com \
--cc=rudalics@gmx.at \
/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).