cannedtuna@lemmy.world to linuxmemes@lemmy.worldEnglish · 2 days agoThe future is now old manlemmy.worldimagemessage-square240linkfedilinkarrow-up1727arrow-down119
arrow-up1708arrow-down1imageThe future is now old manlemmy.worldcannedtuna@lemmy.world to linuxmemes@lemmy.worldEnglish · 2 days agomessage-square240linkfedilink
minus-squareferret@sh.itjust.workslinkfedilinkEnglisharrow-up2·19 hours agoWhat deficiencies does ydotool have for your workflow?
minus-squaremichaelmrose@lemmy.worldlinkfedilinkEnglisharrow-up4·17 hours agoIt’s abandoned it’s GitHub page talks about rewriting in JavaScript in 2024. X actually gets security updates.
minus-squareLimonene@lemmy.worldlinkfedilinkarrow-up1·15 hours agoSending keys to non-active windows without activating them. It looks like ydotool also needs root, and has weird interactions with non-qwerty keyboard layouts. I’ve also been using Autokey lately which has similar blockers with Wayland.
minus-squareJTskulk@lemmy.worldlinkfedilinkEnglisharrow-up1·11 hours agoI switched from autokey to espanso when kde/Wayland forced me to abandon X, I gotta say I really like espanso now. I also use ydotool and it seems fine. I’m writing a kde-specific puautogui replacement right now.
What deficiencies does ydotool have for your workflow?
It’s abandoned it’s GitHub page talks about rewriting in JavaScript in 2024. X actually gets security updates.
Sending keys to non-active windows without activating them.
It looks like ydotool also needs root, and has weird interactions with non-qwerty keyboard layouts.
I’ve also been using Autokey lately which has similar blockers with Wayland.
I switched from autokey to espanso when kde/Wayland forced me to abandon X, I gotta say I really like espanso now. I also use ydotool and it seems fine. I’m writing a kde-specific puautogui replacement right now.