bug#30695: 25.2; Why is emacsclient frame "invisible"?

[Noam Postavsky]

Live System User <nyc4bos@aol.com> writes:

>         While having an Emacs daemon running, i created an Emacs client
>         via "emacsclient -c file`.txt".  I then switched to a different
>         (GTK3) workspace and from a terminal there I attempted to
>         create another Emacs client via "emacsclient -c file2.txt".  I
>         did not see a newly created Emacs client frame in this
>         workspace.

Is Emacs burning CPU while this is happening?

Does this only happen when opening a frame through emacsclient?  E.g.,
if you evaluate

    (progn (sleep-for 3) (make-frame))

and then quickly switch to another workspace, do you see similar
behaviour?

>         This is probably a window manager glitch that Emacs
>         can't do alot about except maybe the following:
>
>         1.  Provide a way for users to specify which
>             workspaces to create Emacs client frames on
>             and, optionally default to the "current" workspace
>
>         2.  Optionally. switch to that workspace

I don't think Emacs can do either of these, since workspaces are a
window manager-specific concept.