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: 44961@debbugs.gnu.org, Lars Ingebrigtsen <larsi@gnus.org>,
Stephen Berman <stephen.berman@gmx.net>
Subject: bug#44961: 28.0.50; [feature/pgtk] frame-position returns incorrect information
Date: Mon, 21 Feb 2022 19:28:27 +0800 [thread overview]
Message-ID: <87sfscfoh0.fsf@yahoo.com> (raw)
In-Reply-To: <874k4slb9d.fsf@gmail.com> (Robert Pluim's message of "Mon, 21 Feb 2022 12:17:18 +0100")
Robert Pluim <rpluim@gmail.com> writes:
> Stephen> This sounds like bug#52697, which was fixed on master in 855928082b and
> Stephen> 9966d9574b.
> It does, but I think that only fixed part of the issue. With
> GDK_BACKEND=x11, I get the right results, but with the Wayland backend
> I always get "(26 . 23)" wherever I place the frame(although if I
> maximize the frame I get "(0 . 0)"
Could you tell the result with an undecorated frame?
> This might be an effect of the Wayland coordinate system insanity that
> they've foisted on the rest of the world.
I tend to agree.
next prev parent reply other threads:[~2022-02-21 11:28 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
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 [this message]
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=87sfscfoh0.fsf@yahoo.com \
--to=bug-gnu-emacs@gnu.org \
--cc=44961@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=luangruo@yahoo.com \
--cc=rpluim@gmail.com \
--cc=stephen.berman@gmx.net \
/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).