André Paiusco

@chrysle my bad, I'll remove the parameter fix, but will leave only the Arch addition then.

Should it be added to the changelog even tho it doesn't affect the end users? I don't see a reason to flood the changelog just for adding a new instruction...

Pretty much sorry for that and for disappearing for so long. Hopefully now my smaller PR #252 cleans a bit more without making it impossible to use. We should consider...

does `ydotool --version` gives you something? If not, `ydotoold --version` gives you something? It seems you're using 1.0.4 (https://build.opensuse.org/package/show/openSUSE%3AFactory/ydotool) But as the error message shows, ydotoold is creating the `/run/user/0/.ydotool_socket`...

No, you don't need to do that, as the systemd .service comes with it. When you compile, you can even define on CMake if you want a system user service...

@g-h-97 ydotool does support you defining the socket path, it actually queries for an env var named `YDOTOOL_SOCKET`. It only goes for the "hardcoded" one if you don't define the...

@g-h-97 not necessarily (even tho for now that forces you to recompile it), this was addressed at #237. So you can make the service as a system with a CMake...