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 13:20:39 +0200 [thread overview]
Message-ID: <877d2gu4u0.fsf@gnus.org> (raw)
In-Reply-To: <87r162wweb.fsf@yahoo.com> (Po Lu's message of "Tue, 12 Apr 2022 16:14:52 +0800")
Po Lu <luangruo@yahoo.com> writes:
> It's because the responsible code was commented out, probably sometime
> after the release of 27.1. Please try the following patch (I suspect
> the didExitFullScreen bug alluded to in the comment is also related to
> using emacs_event somehow):
[...]
> + ie.kind = MOVE_FRAME_EVENT;
> + XSETFRAME (ie.frame_or_window, emacsframe);
> + XSETINT (ie.x, emacsframe->left_pos);
> + XSETINT (ie.y, emacsframe->top_pos);
I tried the patch on Macos now, and it did not fix the problem. I.e.,
the move-frame-functions hook was not called when I moved the frame.
next prev parent reply other threads:[~2022-09-06 11:20 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877d2gu4u0.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 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.