ydotool VS tessen

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

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

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.

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.

ydotool is the generic equivalent. It works on both X11 and Wayland environments.

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).

Does ydotool do what you need? I haven't even tried Wayland in years. I'm sure someday I'll find the need.

Looks like a known issue.

https://github.com/keepassxreboot/keepassxc/issues/2281

I'm considering adding support for keepassxc in tessen but autotype works only on wlroots based compositors like sway right now.

https://github.com/ayushnix/tessen/issues/19

This may not be as impressive but I wrote a script to eliminate one of the primary roadblocks I faced when I moved to Wayland on my Linux desktop — a script to copy and autotype password store amd gopass data, kinda like rofi-pass

https://github.com/ayushnix/tessen

tessen is a bash script to autotype and copy password store data on wayland compositors. The latest release of tessen adds support for gopass as well, although parsing YAML files isn't supported. If gopass files use the same format mentioned here, tessen should work fine.

I'd be willing to package it for Void Linux but I don't really have any experience with how Void Linux packages work. tessen is just a shell script so you can download it and place it in your $PATH and use it if you want.

As I've mentioned in the isse tracker here, the only thing that's missing from fuzzel is support for using a configuration file. If it gets that, it would replace every other launcher and dmenu program on Wayland for me and would also allow me to go ahead and brand fuzzel as the default dmenu backend for tessen.

I made this post a few weeks ago about tessen's initial release. Since then, I've added a few features that might've prevented rofi-pass users from switching to Wayland based compositors (I was one of them).

I ran into this problem as well when making tessen. fzf doesn't have a GUI like rofi, bemenu, and wofi do, so you can't use fzf to type in data in anything else besides the terminal in which it was opened, at least not without resorting to ugly hacks (which is what the swaymsg window move method is).

Support for wofi has been added as well