GNU bug report logs - #44961
28.0.50; [feature/pgtk] frame-position returns incorrect information

Previous Next

Package: emacs;

Reported by: Robert Pluim <rpluim <at> gmail.com>

Date: Mon, 30 Nov 2020 14:34:02 UTC

Severity: normal

Tags: moreinfo

Found in version 28.0.50

Done: Robert Pluim <rpluim <at> gmail.com>

Bug is archived. No further changes may be made.

Full log

Message #65 received at 44961 <at> debbugs.gnu.org (full text, mbox):

From: Robert Pluim <rpluim <at> gmail.com>
To: Po Lu <luangruo <at> yahoo.com>
Cc: 44961 <at> debbugs.gnu.org, Lars Ingebrigtsen <larsi <at> gnus.org>,
 Stephen Berman <stephen.berman <at> gmx.net>
Subject: Re: bug#44961: 28.0.50; [feature/pgtk] frame-position returns
 incorrect information
Date: Mon, 21 Feb 2022 12:49:48 +0100

>>>>> On Mon, 21 Feb 2022 19:28:27 +0800, Po Lu <luangruo <at> yahoo.com> said:

    Po> Robert Pluim <rpluim <at> 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)"

    Po> Could you tell the result with an undecorated frame?

If I create a second frame with

(make-frame '((undecorated . t)))

then

(frame-position) => (0 . 0)

wherever that frame is positioned.

Robert
--
This bug report was last modified 3 years and 87 days ago.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.