From: Robert Pluim <rpluim@gmail.com>
To: Yuuki Harano <masm+emacs@masm11.me>
Cc: 44961@debbugs.gnu.org
Subject: bug#44961: 28.0.50; [feature/pgtk] frame-position returns incorrect information
Date: Mon, 04 Jan 2021 19:15:04 +0100 [thread overview]
Message-ID: <878s9836xj.fsf@gmail.com> (raw)
In-Reply-To: <20201220.024228.1032082898181723362.masm@luna.pink.masm11.me> (Yuuki Harano's message of "Sun, 20 Dec 2020 02:42:28 +0900 (JST)")
Yuuki Harano <masm+emacs@masm11.me> writes:
> Pgtk emacs doesn't receive events when a window moves, so it can't update the position data.
>
> Also, wayland support code in Gtk ignores gtk_window_move for toplevel windows, so pgtk emacs can't move the window.
Yes, this is the conclusion I came to as well, from reading various
comments by the Wayland developers about how the new paradigm was that
end users are not allowed to know about frame-positions, since thatʼs
Old School(™), and they're New School(™), and normal people who like
to think in coordinate systems are WRONG!
(Iʼm paraphrasing :-) )
It would be nice if frame-positioning on initial frame-creation worked
correctly, since desktop.el does that (I haven't checked if thatʼs
true or not).
Robert
next prev parent reply other threads:[~2021-01-04 18:15 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-30 14:33 bug#44961: 28.0.50; [feature/pgtk] frame-position returns incorrect information Robert Pluim
2020-12-01 9:15 ` Robert Pluim
2020-12-19 17:42 ` Yuuki Harano
2020-12-20 7:45 ` martin rudalics
2020-12-20 10:13 ` Yuuki Harano
2020-12-21 15:33 ` martin rudalics
2021-01-04 18:15 ` Robert Pluim [this message]
2021-01-05 13:24 ` Robert Pluim
2021-01-05 15:32 ` martin rudalics
2021-01-05 16:00 ` Robert Pluim
2021-01-01 8:41 ` Yuuki Harano
2021-01-01 10:19 ` martin rudalics
2021-01-03 9:04 ` Yuuki Harano
2021-01-03 9:23 ` martin rudalics
2022-02-20 14:07 ` Lars Ingebrigtsen
2022-02-20 19:57 ` Stephen Berman
2022-02-21 11:17 ` Robert Pluim
2022-02-21 11:28 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-21 11:46 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-21 12:58 ` Robert Pluim
2022-02-21 13:26 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-21 14:50 ` Robert Pluim
2022-02-21 11:49 ` Robert Pluim
2022-02-21 11:55 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-21 1:22 ` Po Lu 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=878s9836xj.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=44961@debbugs.gnu.org \
--cc=masm+emacs@masm11.me \
/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).