this post was submitted on 08 Jul 2026
239 points (99.6% liked)
Linux
14286 readers
236 users here now
A community for everything relating to the GNU/Linux operating system (except the memes!)
Also, check out:
Original icon base courtesy of lewing@isc.tamu.edu and The GIMP
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
At those times I'm fucking glad I overengineered my autoclicker script. This means, once Wayland hits me, switching from xdotool to ydotool won't cause me too much pain. (Most of the script stays as it is, only base functions like "Click" get remade. And yes, I'm lazy.)
I'd call that plain engineering; you've separated out the independent logic from the point where it actually touches the system. That's how stuff should be built and operate.
What kinds of things do you guys automate?
mkvtoolnix-gui. I'm often editing anime episodes; adding/removing subtitles, removing non-native audio, removing those "ENCODED BYJOHN SMITH", etc. Often the checkboxes I need to click are predictably placed, so I use an autoclicker to do it once instead of clicking multiple checkboxes 12~24 times in a row.Ah, I hadn’t even considered that Xdotool would be… well for X11. Thanks mentioning this, so I’ll know what the problem is next time I try to use my auto clicker script and it doesn’t work.
Yup.
On a lighter side, apparently ydotool has a smarter design; instead of sending events to the X server like xdotool does, it emulates an input device. This means you can start using it before migrating to Wayland, and in case the Linux community eventually deprecates Wayland for something else, it should still work.
Now I just need a Wayland equivalent to grabc. A lot of my autoclicker scripts relies on it for dynamic behaviour, like "keep clicking
$pixel1until$pixel2changes colour".