-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature Request: Support for wayland. #18
Comments
Seems like this need to be requested in |
My understanding of Wayland is that it's a completely new protocol that replaces the X protocol. If that's the case then both wmctrl and jumpapp would probably have to be re-written from scratch to support Wayland. (If I did it again I'd probably re-write jumpapp in go-lang instead of relying on / wrapping wmctrl.) Maybe someone more knowledgeable can comment on how much work it would be. Out of curiosity, what distro/version are you using that has Wayland on it? |
Yes, most likely, Wayland is now on the phase where I can use it everyday(at least on the desktop side), but I've been using jumpapp for quite some time that it's breaking my habits of easily switching applications. I'm using Gnome on ArchLinux. |
On GNOME and Wayland I've used the AppKeys GNOME extension successfully. The version on extensions.gnome.org is a bit old and doesn't support customizing the hotkeys. See issue #38 for how to customize hotkeys in the development version. |
Recently, I've started to use Ubuntu17.10/GNOME3 on Wayland and needed to restore jumpapp functionality. (I'm not a fan of using gnome3 dock to preserve place on the screen so AppKeys wasn't for me.) This new extension allow you to define the list of applications you want to jump, specifying what to launch if the application is not running yet. (Or to define any custom shortcuts.) Hence, you can jump to quite difficult things, e.g. this calendar as chrome application:
Regular expressions for satisfying your deepest wishes included. Everything is stored in a file you can easily back up. |
for Gnome, another approach used by gnome-magic-window is the dbus interface to for example: |
Excuse me if I'm wrong @khimaros , but it sounds like gnome-magic-window is an exact replacement for |
Hi! Is there any update on this? Every time I hear the word It's development has been slow, but I guess that in some years it will eventually replace X11, specially as some mainstream distros like Ubuntu started to roll it out. But I'm trying to figure out the current landscape of tools in Wayland, as I do not want to try it out unless most (or all) of the tools I use, like This is just to know if any of you has a mid-term view on this topic, including |
Could this be an inspiration for a future solution? https://unix.stackexchange.com/questions/656729/wmctrl-like-tool-or-alternative-for-kde-wayland |
Can confirm the run-or-raise gnome extension mentioned in #18 (comment) is a perfect replacement that works for all my applications - both Wayland native and not. In addition, it is extremely responsive and low latency. Here is what I ended up with in my
The key sequences are X11 keysyms https://wiki.linuxquestions.org/wiki/List_of_keysyms with modifiers https://github.com/CZ-NIC/run-or-raise#shortcut, then the next two fields are the program name and optionally wmclass that is used to find existing windows of the application. Check the documentation, it is excellent. |
the ww alternative for kde plasma has now its own github project page https://github.com/academo/ww-run-raise Also, a couple of other alternatives to tools such as wmctrl and xdotool that are supposed to work on wayland https://github.com/ReimuNotMoe/ydotool this last one seems like the most adequate |
As what the title says, here's the log when I tried to run it in
Wayland
:The text was updated successfully, but these errors were encountered: