ydotool
Our great sponsors
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
dotfiles
-
Getting a menu on right-click of the title-bar (but not on background!)
Here's how to do it - in this example, I'm using my sway-menu python script to generate the menu itself. I'm also moving the menu to be near the cursor:
-
Remotely starting graphical app inside Sway session, when the app needs to run as root, without relying on authentication from within the session
Maybe try my script sway-runner
-
Using nwg-wrapper for a HUD of help for sway modes
As a geriatric user of sway, I don't always remember the keystrokes in the more esoteric corners of my configuration. I find that my script sway-menu helps with the bulk of the uncommon key bindings. But when I drop into a 'mode' (eg "move" mode) I don't always remember all the clever things I programed into it.
-
Is it possible to have my Bluetooth controller disconnect automatically on idle?
I wrote a simple bash script bluetooth-timeout to power-off the linux bluetooth stack after 10m of activity. Maybe this would help you.
-
What do I need to install on the Sway spin?
Another source for ideas is to read through the configs and scripts written by others. I offer my own here - there are many others around.
-
Application To Display Keybinds On-screen
sway-menu
-
Digital overlay clock?
Here's a script that uses nwg-wrapper to display a countdown - it would be easy to modify it to display a digital clock.
-
Sway productivity tips
Imma gonna browse through your stuff to see if there's a scratch to a hitherto unnoticed itch that I can snarf. You might like to do the same with my dotfiles - particularly bin/sway-\, *.config/sway** and .config/waybar.
-
Anyone know how to move container to the next *empty* workspace?
You might be able to modify my sway-next-empty-workspace script for that. Maybe see if changing swaymsg to i3-msg does the job.
-
Password manager solution in Wayland?
I use myclipman to wrap clipman with wayland/swaywm to prevent passwords being cached.
ydotool
- Show HN: Bonk, a command-line tool for X11 window management
-
Improving cursor rendering on Wayland
Wayland provides little by design, so this is quite typical. For example:
Screensharing is handled by pipewire [0], changing keyboard layouts aren't defined [1] by wayland, and generally anything Wayland devs think would 'corrupt' their protocol.
They leave most things to the compositor to implement, which leads to significant fragmentation as every compositor implements it differently.
Long gone are the days of xset and xdotool working across nearly every distro due to a common base, now the best you'll get is running a daemon as root to directly access `/dev/uinput` [2] or implementing each compositors accessibility settings (if they have them) as a workaround.
[0] https://superuser.com/questions/1221333/screensharing-under-...
[1] https://unix.stackexchange.com/questions/292868/how-to-custo...
[2] https://github.com/ReimuNotMoe/ydotool
-
how hard is it to program pinch zoom for my touchpad in linux?
I personally use libinput-gestures to call commands using touchpad gestures. You can also combine it with ydotool to bind macros and such to your gestures, e.g. 4 fingers swipe down closes the current window, 3 fingers swipe left or right changes workspace, etc
-
ydotoold background process?
Have you tried using the systemd unit file supplied with ydotool? It's probably installed somewhere on your system. Else you can get it here and just change the install location of ydotoold.
-
KDE-Connect keyboard input works on Wayland now!!
For simulated keyboard there are tools such as dotool or ydotool and KeePass extensions such as KPUInput that work by giving the user access to /dev/uinput. That works, but it's a bit inelegant; I guess in the future a Wayland protocol for simulated keyboard input will emerge, like wlroots already has, also for virtual pointers.
-
Out of curiosity, I tried to use Wayland earlier and compared to X11, everything seems to load faster which really surprised me. However, I've also noticed some things that confused me, that's why I'm posting this. To ask what I'm missing or what I did wrong. Thanks as always!
ydotool is the generic equivalent. It works on both X11 and Wayland environments.
-
Curious to know what are your general experiences on using keyboard and mouse input automations on Wayland...
Autokey does not work yet, but there is Hawck and Espanso that you could play around with. And there is ydotool if all you need is simulating basic input (as in ydotool mousemove -x -10 -y -10, ydotool type 'Hello world!' and so on).
-
Asahi Linux To Users: Please Stop Using X.Org
Does ydotool do what you need? I haven't even tried Wayland in years. I'm sure someday I'll find the need.
- Somehow AutoHotKey is kinda good now
- How to emulate mouse clicks with keyboard shortcuts
What are some alternatives?
i3status-rust - Very resourcefriendly and feature-rich replacement for i3status, written in pure Rust
xdotool - fake keyboard/mouse input, window management, and more
sway-gnome - Opinionated Sway Configuration using GNOME session services, for GNOME >= 3.34
wtype - xdotool type for wayland
sway - i3-compatible Wayland compositor
AutoKey - AutoKey, a desktop automation utility for Linux and X11.
openSUSEway - dotfiles for Sway on openSUSE
evsieve - A utility for mapping events from Linux event devices.
picom - A lightweight compositor for X11 (previously a compton fork)
cage - A Wayland kiosk
key-mapper - 🎮 An easy to use tool to change the mapping of your input device buttons. [Moved to: https://github.com/sezanzeb/input-remapper]