unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: martin rudalics <rudalics@gmx.at>
To: Madhu <enometh@meer.net>, emacs-devel@gnu.org
Subject: Re: Deiconifying GTK frames on GNOME shell
Date: Fri, 10 Sep 2021 10:34:17 +0200	[thread overview]
Message-ID: <366d9251-3609-9e0b-3d35-8af409af706a@gmx.at> (raw)
In-Reply-To: <m3fsudhoyq.fsf@leonis4.robolove.meer.net>

 > [I thought I posted this workaround that I've been using at least since

... when? ...

 > - either on a bugreport or in a message to you - but I can't spot it in
 > my XMAIL]

Have we been discussing this issue before?  Have you (or anyone else)
filed a report against it?  No pointers anywhere?

 > (defadvice make-frame-visible (around mutter-workaround (&optional frame) activate)
 >    (if (or (eql (frame-parameter frame 'visibility) 'icon)
 > 	   (eql (frame-parameter frame 'visibility) nil))
 >        (set-frame-parameter frame 'visibility nil))
 >    ad-do-it)

This works here for making the frame visible again.  It fails for
`raise-frame' and `select-frame-set-input-focus' but I think it should
be possible to fix these with similar advices too.

I don't understand yet how this x_make_frame_visible_invisible stuff is
supposed to work in the first place and I haven't even found the commit
that introduced it yet.  Maybe it got fixed or broken during

https://lists.gnu.org/r/emacs-devel/2018-03/msg00863.html

so there should be also a timeout around somewhere.

IIUC this could be a serious issue with frame switching on mutter so
maybe either other people use a workaround like yours or they use a
version of mutter where this problem doesn't happen.

martin



  reply	other threads:[~2021-09-10  8:34 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 [this message]
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=366d9251-3609-9e0b-3d35-8af409af706a@gmx.at \
    --to=rudalics@gmx.at \
    --cc=emacs-devel@gnu.org \
    --cc=enometh@meer.net \
    /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).