From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Augusto Stoffel <arstoffel@gmail.com>
Cc: 53793-done@debbugs.gnu.org
Subject: bug#53793: 29.0.50; 'fullscreen' frame parameter on pgtk
Date: Sun, 06 Feb 2022 17:38:14 +0800 [thread overview]
Message-ID: <87czk0pc6x.fsf@yahoo.com> (raw)
In-Reply-To: <875ypspe4n.fsf@gmail.com> (Augusto Stoffel's message of "Sun, 06 Feb 2022 09:56:24 +0100")
(When replying to bug reports in the future, please use "Reply to All",
so that your messages can be recorded by the bug tracker.)
Augusto Stoffel <arstoffel@gmail.com> writes:
> Yes, the frame parameter is correctly reported now, thanks!
I'm closing this bug then, thanks.
> It also seems that `move-frame-functions' are not run as promised. Or
> at least the following bit of configuration is still broken on pgtk but
> works fine on X.
If you're running Wayland, then it's a limitation of the Wayland
protocol, which has no global coordinate system. GTK exposes it as
every Wayland window (surface) being placed at 0, 0.
> (add-hook 'move-frame-functions
> (lambda (frame) "Undecorate frame when maximized."
> (set-frame-parameter frame 'undecorated
> (eq 'maximized (frame-parameter frame 'fullscreen)))))
next prev parent reply other threads:[~2022-02-06 9:38 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-05 8:50 bug#53793: 29.0.50; 'fullscreen' frame parameter on pgtk Augusto Stoffel
2022-02-06 0:59 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
[not found] ` <875ypspe4n.fsf@gmail.com>
2022-02-06 9:38 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-02-06 10:02 ` Augusto Stoffel
2022-02-06 14:02 ` Stephen Berman
2022-02-07 1:23 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-07 19:33 ` Augusto Stoffel
2022-02-08 0:53 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-08 8:56 ` martin rudalics
2022-02-09 8:20 ` Augusto Stoffel
2022-02-09 8:45 ` martin rudalics
2022-02-09 13:35 ` Augusto Stoffel
2022-02-09 18:25 ` martin rudalics
2022-02-10 7:43 ` Augusto Stoffel
2022-02-07 22:33 ` Stephen Berman
2022-02-08 0:53 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-08 10:24 ` Stephen Berman
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=87czk0pc6x.fsf@yahoo.com \
--to=bug-gnu-emacs@gnu.org \
--cc=53793-done@debbugs.gnu.org \
--cc=arstoffel@gmail.com \
--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).