From: "夜坂雅 via Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Po Lu <luangruo@yahoo.com>
Cc: whainte@outlook.com, Lars Ingebrigtsen <larsi@gnus.org>,
55836@debbugs.gnu.org
Subject: bug#55836: 29.0.50; (iconify-frame) freezes buffer view under Wayland.
Date: Mon, 05 Sep 2022 17:57:26 +0800 [thread overview]
Message-ID: <874jxm87p5.fsf@disroot.org> (raw)
In-Reply-To: <87czcbcnhp.fsf@yahoo.com>
Po Lu <luangruo@yahoo.com> writes:
> That's to be expected. It turns out that programmatically deiconifying
> a window isn't supported by the Wayland protocol (see here:
> https://wayland.app/protocols/xdg-shell#xdg_toplevel is missing a
> function corresponding to "SetMinimized" to disable the minimized
> state), so GDK and Emacs don't support it either.
😅
>>> But when I apply your patch, running
>>>
>>> $ emacsclient -e '(iconify-or-deiconify-frame)'
>>>
>>> and deiconify it using taskbar, the bug happens.
>
> I'm not sure what you mean by that.
1. Apply your said patch and build Emacs.
2. Run emacs and M-x server-start.
3. Run emacsclient -e '(iconify-or-deiconify-frame)' to iconify it.
4. Deiconify it. This window won't refresh when I try to run Emacs
tutorial from the menu bar.
> What happens if you comment out every call to `SET_FRAME_ICONIFIED' in pgtkterm.c?
The bug can still happen, which means even commenting every call to
SET_FRAME_ICONIFIED, Emacs is still unable to update frame when
iconified using C-z.
next prev parent reply other threads:[~2022-09-05 9:57 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-07 18:06 bug#55836: 29.0.50; (iconify-frame) freezes buffer view under Wayland koaaa.outlook
2022-06-08 0:32 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-19 22:09 ` whainte
2022-06-20 0:51 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-23 8:40 ` Lars Ingebrigtsen
2022-09-01 11:26 ` 夜坂雅 via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-02 9:31 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-03 4:46 ` 夜坂雅 via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-03 5:01 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
[not found] ` <166219690756.47038.8534222496369366592@localhost>
2022-09-04 11:01 ` 夜坂雅 via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-04 12:50 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-05 9:57 ` 夜坂雅 via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-09-05 14:08 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
[not found] <c49677c5-8fe8-6038-7776-f42b5fba91e4@gmail.com>
2022-09-25 12:06 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
[not found] ` <b5a17ec6-345-9df5-f5d3-1f1c803d6e8c@gmail.com>
2022-09-25 12:33 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
[not found] ` <d3757b8e-8699-fe39-3534-f01789bedaf@gmail.com>
2022-09-26 0:15 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
[not found] ` <c128677a-64b0-ba6f-4a6-df9a3e02b61@gmail.com>
2022-09-27 0:25 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-28 15:06 ` Tino Calancha
2022-09-29 0:21 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-30 12:36 ` Tino Calancha
2022-09-30 13:17 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-03 12:28 ` Tino Calancha
2022-11-09 12:28 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-10 10:59 ` Tino Calancha
2022-11-10 11:50 ` 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=874jxm87p5.fsf@disroot.org \
--to=bug-gnu-emacs@gnu.org \
--cc=55836@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=luangruo@yahoo.com \
--cc=shadowrz@disroot.org \
--cc=whainte@outlook.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).