André Paiusco

@shellheim I think there are some improvements. I'm wondering that even the `ydotool.service` is now named `ydotoold.service` You also don't need to `chown` on the socket created, ydotoold accepts this...

@Edwardius if you look at #233 you'll see that the package that debian-like distro currently ships is 5years old, so this is controlled by the distro/repo and not by us....

Do you know how easy it is to create a `ydotoold.socket`? It's still on my list to read about that and see how to create it

@YHNdnzj I've been reading a bit on socket creation [in the docs](https://www.freedesktop.org/software/systemd/man/latest/systemd.socket.html#) I was wondering if the `ListenSpecial=/dev/uinput` would be the way to go, but then there's nothing coming from...

No, wait, but that's not the issue mentioned on #221. The issue there is that `ydotoold` somehow is starting so fast that `/dev/uinput` is still unavailable, hence the `failed to...

oh, so you mean that the first call from the CLI will start the daemon... and then the `.socket` creates the socket file that the daemon will be attached to....

I liked it! I'll soon try it out, what do you recommend for the case where one is either starting ydotoold manually or not using systemd? I don't want it...

@ReimuNotMoe maybe this can be fixed somehow? Or add a check if this is the case on `/dev/uinput` we can at least let the user know what to do? What...

The change is less simple than I expected, we either make `ydotool.c` be aware of the helps for each command, or things starts to get ugly. I think making the...

why `mousemove -w -- ` was not working for you? Seems to me that your change would cause the same result (haven't test it that yet)