In GNOME Shell (Wayland edition), Equake does not properly appear on top when invoked.
I think there is a possible workaround for this.
If an Emacs daemon is running, then even in GNOME Shell running on Wayland, a call to emacsclient -c --eval "(progn (select-frame-set-input-focus (selected-frame)))" creates an Emacs frame which appears on top of current windows.
Using equake-use-frame-hide set to nil (destruction of frame on "close") (requiring https://gitlab.com/emacsomancer/equake/-/issues/26 to be fixed) and a shortcut command which checks for a current Equake frame (and runs regular equake-invoke in that case) and otherwise runs an expanded version of emacsclient -c --eval "(progn (select-frame-set-input-focus (selected-frame)))" which transforms the created Emacs frame into an Equake frame seems like it could be a workaround for Wayland behaviour.
In GNOME Shell (Wayland edition), Equake does not properly appear on top when invoked.
I think there is a possible workaround for this.
If an Emacs daemon is running, then even in GNOME Shell running on Wayland, a call to
emacsclient -c --eval "(progn (select-frame-set-input-focus (selected-frame)))"creates an Emacs frame which appears on top of current windows.Using
equake-use-frame-hideset tonil(destruction of frame on "close") (requiring https://gitlab.com/emacsomancer/equake/-/issues/26 to be fixed) and a shortcut command which checks for a current Equake frame (and runs regularequake-invokein that case) and otherwise runs an expanded version ofemacsclient -c --eval "(progn (select-frame-set-input-focus (selected-frame)))"which transforms the created Emacs frame into an Equake frame seems like it could be a workaround for Wayland behaviour.