12:24 <leon-p> FWIW I have no issue with people wanting to use something other than systemd, my issue is with people who can't name a reason other than vague ramblings about "minimalism"

12:42 <daurnimator> wooo, time to try river again soon; I'm no longer an nvidia user!

12:51 <bwbuhse> that’s fair. I only use OpenRC because I like Gentoo and it (Gentoo) makes sense to me and, on Gentoo, OpenRC is just the default init. In general, I also don’t love journalctl but I’m sure there are ways I could deal with that if I were in systemd

13:26 <szgy> yeah, trying a different non systemd distro was basically just curiosity

13:52 <dmcblue> So bit of noobie confusion, I tried adding swayidle to turn off the screen, but I keep getting `[swaymsg/main.c:497] Unable to retrieve socket path`  after the idle period.  From what I can research, I need to set the sway socket path in SWAYSOCK, but I thought that would be available if running sway, not river. I think I'm missing something

13:52 <dmcblue> basic about how river interacts with the recommended software add-ons in the README. This is on Arch, if the distro is relevant; haven't found anything in the logs here https://codeberg.org/river/wiki/src/branch/master/pages/Recommended-Software.md

13:55 <vyivel> dmcblue: how are you running swayidle?

13:56 <dmcblue> I was just trying to test it out in the command line, will post config and command

13:56 <dmcblue> $ cat .swayidle/config

13:56 <dmcblue> timeout 120 'swaymsg "output * dpms off"' resume 'swaymsg "output * dpms on"

13:56 <dmcblue> exec swayidle -w &

13:57 <dmcblue> Do I need another dispatch/message service other than swaymsg?

13:58 <vyivel> yes

13:58 <vyivel> see wlopm

14:13 <dmcblue> Oh great, thanks so much! Works perfectly now