For me AutoKey is absolutely essential to my workflow. I have tons of text expansions and shortcuts to “remap” keys. E.g., respectively, typing dAt expands into 2025-05-08, 13:47:40 CEST, and pressing alt + k simulates the arrow down key.
Secondly there’s XScreenSaver which has so many wonderful (mathematical) visualizations that it would be a damn shame if these eventually get lost as Wayland gets more adoption.
None of these have Wayland alternatives as far as I know. For text expansion there’s Espanso, but it doesn’t support keyboard shortcuts yet.
You must log in or register to comment.
I used to have issues with middle click scroll, but my own solution works fine and it works on Wayland and X11 too
autokey
I accomplish the same thing with compose sequences, and by binding a keyboard shortcut in my desktop to call a script with
wtype. It’s not a cross-compositor solution though, as you’d have to manually setup binds in each of them.I don’t see much hope for this one-to-one unfortunately.
ydotool iirc
Check out xremap https://github.com/xremap/xremap
AwesomeWM, and xdotool.
That’s it. Oh and x-eyes of course
Have you tried ydotools, which works on both Wayland and X?
New hyprland patch can do pretty much all the xdotool stuff since they added a send key to window thing
There’s ydotool.
I find it’s not as reliable in targeting inputs, and you sometimes need to set the XDG_RUNTIME variable yourself.
wtypeis much better at this, but is limited to keystrokes
You might be interested in river as a awesome replacement:
what do you use x-eyes for?
I don’t think that was entirely serious…
👀
https://www.x.org/releases/X11R7.5/doc/man/man1/xeyes.1.html
Xeyes watches what you do and reports to the Boss.
Network transparency
Gnome. No shell restart on wayland, and not planned.
Pardon?
GNOME defaults to Wayland. GNOME 49 is going to remove X11 support all together.
Xfwm. Taskbars are now wayland, but don’t autohide without the compositor supporting it.
Easystroke https://github.com/thjaeger/easystroke, please, please, please somebody pick the project, I’ll gladly pay a license to use it.
https://github.com/jersou/mouse-actions
It’s recommended by the easystroke dev too: https://github.com/thjaeger/easystroke/wiki
I tried Mouse Actions many times, just a different beast (many Easystroke users have the same opinion).
urxvt, bspwm, sxhkd, and many small utilities that I built my desktop with. It’s hard to reproduce the same setup.
XMonad
Couldn’t use xset to manually set some monitors to standby So I searched how to change it back to X.
Also you couldn’t set display variable to another computer’s ip address (a windows one running xming)
Stumpwm. The most ergonomic tiling window manager I know, fantastic configurability like emacs.
keepassxc’s autotype
also, nvidia
KeepassXC work fine on Wayland with xwayland
There are still some quirks but it’s been generally fine for me with Nvidia, almost a year now.
i heard about that. sadly my gpu is so old the latest driver that supports it is the 470 driver
Well, you can hold onto that GPU for a little longer with X11. But it seems you’ll need an upgrade some time later. Though if you don’t game (aside from FOSS ones), Nouveau driver should do the job for your daily needs. However, it still needs time for Wayland.
the nouveau driver works fine except when it crashes for no clear reason after some hours of usage
Even on X11? I tried it on Wayland months ago to see its state and it was generally fine except gaming. Though the results still might depend on the card in use I guess.
Even on X11?
yup. i think it had something to do with video calls or screen sharing, which are essential at work
Hey, I’m in the same boat. Gigabyte GTX 670. Wayland was a sluggish mess, and same goes for nouveau with X11.
I bit the bullet after eight months of running Arch like this, and experimenting around with newer iGPUs in laptops, and bought a new radeon finally. Time to retire this ancient piece of tech.
670 is still better than nothing.
Hopefully it can find its way to someone else’s home on the cheap and still give them plenty of years of fun.
Every time I build a new box or do an upgrade, I try selecting Plasma on Wayland from the login screen. Every time it doesn’t work, I select X11, and never think of it again for another six months to two years.
Must have been a long time since you built a box.
Two years, then the drive exploded a couple weeks ago and I rebuilt it just now. Doesn’t work out of the box, X11, does, so I’ve never looked into it.
Session restore
For me is the lack of virtual displays is Wayland.
I’m using a 49" monitor (with i3) and split it into virtual monitors/displays. For some tasks two displays are good, for others three, and all doesn’t need to be the same size.
The reason for not using i3 splits is that many programs have fullscreen functions that I often use.
Watching a movie is one example, where I have a script that automatically calculate the optimal width without borders and gives me an extra virtual display beside with whatever’s left.
Hyprland can tell a window to be in fullscreen when in fact, it’s not (it’s called… Fakefullscreen). I binded it to shift+f11 and its become part of my workflow, lol
Uhhh, I’ve been dreaming if this and now I’ve got it!
