all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Alynx Zhou via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: 61710@debbugs.gnu.org
Subject: bug#61710: 30.0.50; frame parameter `(fullscreen . maximized)' does not work with PGTK and emacsclient --create-frame
Date: Fri, 24 Feb 2023 18:21:44 +0800	[thread overview]
Message-ID: <1ab6cf9f-a954-d793-4245-2a9b2a43ff46@suse.com> (raw)
In-Reply-To: <83sfexr5ec.fsf@gnu.org>

So, after taking another afternoon on commenting code or adding 
`message`, the problem is located at the last 2 lines of 
`server-switch-buffer`:

```
     (when server-raise-frame
       (select-frame-set-input-focus (window-frame)))))
```

When I set `server-raise-frame` to `nil`, the newly created frame is 
maximized properly, I am not sure why `select-frame-set-input-focus` 
causes such a bug, but I guess it is related on how PGTK handles focus 
on Wayland (actually I think it should do nothing, because Wayland 
clients are not allowed to grab focus explicitly, but there must be some 
interesting things).

I'd like to find out what's wrong with it tomorrow, but at least I have 
a workaround now!

Alynx





      parent reply	other threads:[~2023-02-24 10:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-22 13:27 bug#61710: 30.0.50; frame parameter `(fullscreen . maximized)' does not work with PGTK and emacsclient --create-frame Alynx Zhou via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-22 15:31 ` Eli Zaretskii
2023-02-22 16:34   ` Alynx Zhou via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-22 17:12     ` Eli Zaretskii
2023-02-22 17:28       ` Alynx Zhou via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-24 10:21       ` Alynx Zhou via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1ab6cf9f-a954-d793-4245-2a9b2a43ff46@suse.com \
    --to=bug-gnu-emacs@gnu.org \
    --cc=61710@debbugs.gnu.org \
    --cc=alynx.zhou@suse.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.