rofi VS ydotool

https://github.com/svenstaro/rofi-calc together with https://github.com/lbonn/rofi (both packaged for openSUSE and perhaps other Linux distros).

Which rofi you run? The original one from https://github.com/davatorium/rofi (which is Xorg base, so it has to start XWayland) or the Wayland-based fork on https://github.com/lbonn/rofi?

Rofi does not support wayland you should use https://github.com/lbonn/rofi

I think this problem can be solved using Rofi-fork-wayland.

There's a rofi fork that's wayland native and works with the thousands of scripts and themes out there: https://github.com/lbonn/rofi

There's a patched fork of rofi that supports wayland that I'm actually using, but linked the upstream in my OP for general reference: https://github.com/lbonn/rofi#wayland-support

There's a rofi fork that works well in Wayland: https://github.com/lbonn/rofi You need to install this instead of standard rofi

Also, this fork of rofi … https://github.com/lbonn/rofi

There are replacements for dmenu: standard is wofi (https://hg.sr.ht/~scoopta/wofi), but it has slightly less functionality (although many people live with it just fine), or there is port of rofi (https://github.com/lbonn/rofi), which is much more capable (you need this fork, the original rofi is X-only). Both of these are packaged in most Linux distributions.

I wrote my own web based LaTeX editor I can use if I want access to my LaTeX files from a different computer, something I never would have been able to do if I hadn't learned how the pieces work together (though I actually use neovim over ssh more often).

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.