02:48 <xaltsc> Hey, is there any point in setting and exporting variables in init ? I thought variables would be accessible when river is running, but it doesn't look like it.

02:50 <xaltsc> I think in older versions, it used to do something and block if the process wasn't quitting (I run a runit instance and iirc, it used to block river)

09:38 <AlmostSurelyRob> Hi,

09:38 <AlmostSurelyRob> I am really sorry, but I've got one of my slow-person question. So I am trying waylock. Compiled from source 1.1.0 and I am running `waylock -ignore-empty-password -log-level debug 2> log.waylock`, but I keep getting `error: PAM authentication failed: Authentication failure`. I am pretty sure that the password is correct. I suppose I am misreading

09:38 <AlmostSurelyRob> something. I am just supposed to type in my password, right? No need for a wake up press? I tried both with and without wake-up key and multiple times too and I can't seem to get it to work.

09:38 <AlmostSurelyRob> I like the simplicity of it, so I'd like to integrate it into my current desktop. Please advise.

09:55 <ifreund> this is probably an issue with your system PAM configuration

09:56 <ifreund> have you installed the waylock PAM config file? does your distro have a system-auth target?

09:59 <AlmostSurelyRob> Thanks. No, I definitely haven't installed the config file and I don't know about system-auth target, so let me chek.

10:02 <AlmostSurelyRob> Right, so this is what got installed into {prefix}/etc

10:03 <ifreund> yeah, Pam will only look in /etc/pam.d by default though I believe

10:04 <ifreund> and if your distro doesnt have a system-auth file in that directory youll have to tweak the waylock file to use login or something else instead

10:04 <ifreund> unfortunately there isnt anything 100% portable across distros here

10:05 <AlmostSurelyRob> There's a file /etc/pam.d/system-auth, is that what you mean?

10:05 <AlmostSurelyRob> (This is Fedora)

10:06 <ifreund> yes, then all you should need to do is copy the waylock pam config file into the same directory

10:53 <cathalo> I have been searching in the man pages but cant find where I can enable window decorations

10:55 <Franciman> cathalo: what about : riverctl csd-filter-add app-id|title pattern

10:55 <Franciman> Add pattern to the CSD filter list. Views with this pattern are told to use client side decoration instead of the default server side decoration. Note that this affects new views as well as already existing ones. Title updates are not taken into account.

10:56 <AlmostSurelyRob> Just to say, it's working. Thanks for the pointers, ifreund.

10:56 <ifreund> no problem!

10:57 <ifreund> xaltsc: if you want an environment variable set for your entire river session you have to set it before starting river

10:57 <ifreund> this is simply how environment variables work on unixy systems

10:59 <cathalo> Franciman: can that be applied globally though ?

11:02 <ifreund> cathalo: what river version are you using?

11:03 <ifreund> the docs Franciman provided are out of date (for 0.2, things have changed in 0.3)

11:03 <Franciman> oh sorry

11:03 <Franciman> i have an older version indeed

11:03 <ifreund> for river 0.3, you might be looking for `riverctl rule-add ssd`

11:03 <Franciman> the new one isn't packaged yet for guix system

11:04 <cathalo> ifreund: 0.2.6

11:04 <ifreund> (which is equivalent to `riverctl rule-add -app-id '*' -title '*' ssd`)

11:04 <cathalo> ahh ok, I am on freebsd, I will see if I can get the port upgraded

11:05 <ifreund> the freebsd port is version 0.3.2 iirc

11:05 <cathalo> thanks !

11:05 <cathalo> ohh right well the binary build is clamped at 0.2.6 i guess

11:06 <cathalo> yeah `river-0.2.6 Dynamic tiling Wayland compositor

11:06 <ifreund> ah, well I don't really know much about how FreeBSD ports work so I can't help you there

11:06 <ifreund> all I know is that it says 0.3.2 here: https://www.freshports.org/x11-wm/river

11:09 <cathalo> thanks, also out of curiousity, assuming you use linux what distro do you use ?

11:10 <ifreund> chimera linux

11:10 <ifreund> https://chimera-linux.org/

11:13 <cathalo> ooh that looks pretty interesting, Ill have to check it out. I have been dissatisfied by linux: hence freebsd

11:16 <ifreund> yeah, I find it quite comfy already even though it's fairly new and the package repositories aren't quite as large yet

11:16 <ifreund> I very much understand being dissatisfied by linux

11:17 <Franciman> i use guix system

11:17 <Franciman> it's pretty cool

11:18 <cathalo> how custom is guix: as compared to nix where your basically forced to install things the nix way (for the most part)

11:19 <cathalo> ifreund: honestly as long as the build toolchain is worked on well that is the most important part, binary packages will always break, having a good system for building software: culture and toochain, is great

11:21 <ifreund> cathalo: Chimera's cports build tooling is in fact the best I've worked with so far: https://github.com/chimera-linux/cports/

11:22 <ifreund> it's so nice to be using python rather than bash for this kind of thing

11:24 <cathalo> pretty similar to freebsd. What I like in freebsd is the ports are the packages they just get built quarterly, and there is no distinction you have to make in the package manager it just kinda works.

11:25 <cathalo> I will say python is a bit nicer than Makefile that you use for freebsd ports, where it is basically a hack

11:25 <ifreund> cports is all the packages for the entire system and gets continuously built for the rolling binary repositories by build servers

11:26 <ifreund> you can also bootstrap the system entirely from source though of course

11:27 <cathalo> that is fun until you reach a package that needs llvm :)

12:27 <Franciman> cathalo: it's quite similar to nix

12:28 <Franciman> but it's also more strict in some ways

12:28 <Franciman> and more elegant in certain aspects, in that it uses scheme for almost everything, even the build scripts

12:28 <Franciman> while nix tends to maek strange bash tricks

12:29 <Franciman> ifreund: what are the prerequisites for bootstrapping the entire system?

12:31 <ifreund> they are listed in the readme iirc

12:40 <Franciman> sankyu

12:46 <cathalo> Franciman: nix has been a pain for freebsd because of the heavy bash usage and linux assumptions

12:47 <Franciman> probably guix is a pain too, becaue it is very nazi about being FSF compliant

12:49 <cathalo> don't how linux fragmentation will be fixed in the future, I am some what pessimistic

12:49 <cathalo> linux needs more userland like the bsd's

13:07 <adamcstephens> nixpkgs could surely be extended to support bsd and there was even an initial effort from a few months ago. i doubt it'll ever move away from bash though

13:49 <cathalo> Ok so I finally built river at the new version, however setting ssd does not add window decorations to foot terminal, in fact setting csd does add decorations (I assume foot has its own decorations?). Is there anything else I need to configure a simple title bar with ssd?

17:47 <Guest47> skibidi

23:55 <Guest40> Hi, I am setting up river and I noticed in the example config some keybinds use a "+" like in "Super+Shift" but others do not like "Super Return". What is the difference?