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: Tue, 7 Sep 2021 03:45:03 +0300 [thread overview]
Message-ID: <c496aa37-e0c6-ae8f-6660-f0c7d789f54f@yandex.ru> (raw)
In-Reply-To: <87e1a3cb-430d-ff6d-6244-6e20bbdced94@gmx.at>
On 06.09.2021 11:32, martin rudalics wrote:
> Even after doing (make-frame-visible frame)?
Yup.
> Just in case can you confirm that the earlier mentioned
>
> (1) In xterm.c swap the calls to
>
> gtk_widget_show_all (FRAME_GTK_OUTER_WIDGET (f));
> gtk_window_deiconify (GTK_WINDOW (FRAME_GTK_OUTER_WIDGET (f)));
>
> (2) When trying to deiconify an iconified frame make it invisible first
> and only then make it visible.
>
> hack would work?
Yes, that seems to work. Consistently.
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)
If I do (1), then doing (2) only once is sufficient.
next prev parent reply other threads:[~2021-09-07 0:45 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 [this message]
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
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=c496aa37-e0c6-ae8f-6660-f0c7d789f54f@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).