From: Dmitry Gutov <dgutov@yandex.ru>
To: martin rudalics <rudalics@gmx.at>, emacs-devel <emacs-devel@gnu.org>
Subject: Re: Deiconifying GTK frames on GNOME shell
Date: Sat, 11 Sep 2021 17:48:01 +0300 [thread overview]
Message-ID: <9f81d10e-147b-8521-8d7f-5fb3d03f701d@yandex.ru> (raw)
In-Reply-To: <5b621645-1d03-d102-f40f-02a07e2d9541@gmx.at>
On 10.09.2021 11:33, martin rudalics wrote:
> > If I don't do (1), BTW, I can do (2) twice, and that also makes the
> frame visible.
> >
> > Meaning
> >
> > (make-frame-invisible frame)
> > (make-frame-visible frame)
> > (make-frame-invisible frame)
> > (make-frame-visible frame)
>
> I attach a patch based on this recipe but it causes (occasionally
> terrible) flickers on other desktops so I would have to special-case it
> on mutter anyway. I still have no good idea what's really going on
> here.
The patch seems to work, fixing the scenario above. Thanks.
Not sure at which step the flickers are supposed to appear - probably in
some more complex scenarios?
Perhaps related to the topic of the discussion: I very rarely use
multiple frames myself (child frames excepted), but I'm happy to help
troubleshoot bugs under GNOME anyway.
next prev parent reply other threads:[~2021-09-11 14:48 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-05 9:39 Deiconifying GTK frames on GNOME shell martin rudalics
2021-09-05 10:26 ` Colin Baxter
2021-09-06 8:31 ` martin rudalics
2021-09-05 19:19 ` Dmitry Gutov
2021-09-06 8:32 ` martin rudalics
2021-09-07 0:45 ` Dmitry Gutov
2021-09-07 8:16 ` martin rudalics
2021-09-09 13:13 ` Madhu
2021-09-10 8:34 ` martin rudalics
2021-09-10 12:04 ` Madhu
2021-09-11 8:38 ` martin rudalics
2021-12-06 15:35 ` Madhu
2021-12-08 11:00 ` martin rudalics
2021-12-08 11:09 ` Po Lu
2021-12-08 16:02 ` Yuuki Harano
2021-12-09 0:28 ` Po Lu
2021-12-09 2:30 ` Madhu
2021-12-09 2:46 ` Po Lu
2021-12-09 9:20 ` Eli Zaretskii
2021-12-08 16:33 ` Madhu
2021-12-09 0:31 ` Po Lu
2021-12-09 2:33 ` Madhu
2021-09-10 8:33 ` martin rudalics
2021-09-11 14:48 ` Dmitry Gutov [this message]
2021-09-11 16:43 ` martin rudalics
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=9f81d10e-147b-8521-8d7f-5fb3d03f701d@yandex.ru \
--to=dgutov@yandex.ru \
--cc=emacs-devel@gnu.org \
--cc=rudalics@gmx.at \
/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).