14:44 <adamcstephens> ifreund: I noticed when bumping waylock in nixpkgs that build.zig still has 1.4.0-dev. looks like both the 1.4.0 tag and master branch still have this

14:44 <adamcstephens> I patched in our package, so no rush on our end, but wanted to give a heads up

16:12 <sewn> "Data too big for buffer (4096 + 12 > 4096)." what is this funky error i get every once in a while on river? i only get it if im just using my browser like normal and foot is killed

16:24 <ifreund> adamcstephens: oh no, whoops

16:31 <adamcstephens> :)

20:13 <aktina> how provide environment variables to river, like, i have a river-run script, exporting a bunch of env variables, but i don't think river inherits that, as when i open up a fire up 'env' command on terminal, i don't see those

20:14 <aktina> *when i fire up 'env' ...

20:14 <aktina> this is my river-run script

20:14 <aktina> https://cl1p.net/rvrrun

20:14 <TheAnachron> You should set those variables inside a profile that gets sourced

20:14 <TheAnachron> Don't do those things in rivers init file.

20:15 <aktina> no, this is not the river init file

20:16 <aktina> like, this is a run script, which is run after i login with my greetd/tuigreet stuff

20:16 <aktina> and this script calls up the river, which sources the init config file

20:16 <TheAnachron> Why not put them inside ~/.bash_profile, ~/.bash_login or such?

20:17 <TheAnachron> I don't think it will work that way, as your SHELL is already populated with variables BEFORE you run that script

20:18 <TheAnachron> So when you log in, these ENV variables are kept and copied to sub-processes

20:21 <aktina> i will try that

20:21 <aktina> :)

20:22 <TheAnachron> I have a file ~/etc/sh/session which has these values which I source on my ~/.bash_profile.