bug.n VS ydotool

There is even a dwm-style extremely comprehensive tiling window manager called bug.n [1], which I downloaded it way back in windows 8 days. Made a lot of changes myself and plan to open source it as a fork. Its too good. And combined with the rest of my AHK scripts, my windows setup turns out to be even more customised than many Linux systems I use.

See my post of my windows setup fooling r/unixporn [2] for how it could look.

[1] https://github.com/fuhsjr00/bug.n

bug.n — Amongst other flavours is a dynamic, tiling window manager, which tries to clone the functionality of dwm

another comment mentioned what you're looking for is a window manager: another for windows is bug.n

So when i said "window manager based Linux" I was mostly referring to the stereotypes of the Linux window manager; which 1 person not even having a mouse; staring apps; moving windows doing everything with their keyboard. If you wanna look a bit more into window managers for windows the only "okay" one that I've personally used is bug.n and for Linux there's tons; but my personal fav is I3

you can implement the wm manager of your dreams in ahk ... in like 500 lines. it's amazing stuff.

you can also go all out: https://github.com/fuhsjr00/bug.n

komorebi recently became the second-most starred dynamic tiling window manager for Windows 10+, behind bug.n, which unfortunately seems to have been officially abandoned as of this past week.

What exists on windows today (bug.n and others) isn't good enough.

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.