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: 73207@debbugs.gnu.org, David Koppelman <koppel@ece.lsu.edu>
Subject: bug#73207: 31.0.50; On PGTK frame outer-position and frame-monitor-workarea wrong.
Date: Sat, 14 Sep 2024 20:08:41 +0800 [thread overview]
Message-ID: <87cyl6phdi.fsf@yahoo.com> (raw)
In-Reply-To: <868qvuh4wh.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 14 Sep 2024 14:05:18 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: David Koppelman <koppel@ece.lsu.edu>
>> Date: Thu, 12 Sep 2024 13:24:04 -0500
>>
>> In a PGTK build of Emacs running on KDE Wayland (versions are below) the
>> position of a frame and the size of the workarea are wrong. These work
>> correctly in non-PGTK builds. For example, (frame-edges nil
>> 'outer-edges) returns (0 0 752 840), even though the top-left of the
>> frame is not over pixel 0,0. In a call to (frame-monitor-attributes) the
>> geometry and workarea dimensions are the same. The workarea is correctly
>> reported as smaller in non-PGTK builds.
>>
>> I'd prefer that these be fixed, but if not they ought to be documented
>> in etc/PROBLEMS.
>
> Po Lu, any comments?
>
> ISTR that we already know about this issue, but for some reason I
> cannot find it in PROBLEMS or anywhere else. What did I miss?
It's impossible to extract these values on Wayland because the protocol
is engineered to withhold them from programs. There are entries for
similar protocol limitations in etc/PROBLEMS (e.g. warping or locating
the mouse pointer), but not the unavailability of frame geometry or
workspace dimensions.
next prev parent reply other threads:[~2024-09-14 12:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-12 18:24 bug#73207: 31.0.50; On PGTK frame outer-position and frame-monitor-workarea wrong David Koppelman
2024-09-14 11:05 ` Eli Zaretskii
2024-09-14 12:08 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2024-09-14 12:18 ` Eli Zaretskii
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=87cyl6phdi.fsf@yahoo.com \
--to=bug-gnu-emacs@gnu.org \
--cc=73207@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=koppel@ece.lsu.edu \
--cc=luangruo@yahoo.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).