14:21 <kztx> How can I be sure that programs spawned by `riverctl spawn` have my env vars? For example, some use API keys I just exported in my .bashrc for now until I get around to fancier secrets management stuff.

14:25 <kztx> I guess I find myself sourcing that file everywhere needed and just assume there's a better way

14:32 <kztx> Not just env vars, shell functions too. I guess this really isn't a river question at all.

14:38 <kztx> I think my confusion lied in that this stuff was handled by using a shebang of `#!/usr/bin/env sh` when I was using bspwm/polybar but the same scripts on river/waybar don't pick them up - but so much else on my system changed too

17:20 <tiosgz> kztx: if it's stuff specific to waybar, i'd make a launcher script so that it's nowhere else

17:21 <tiosgz> otherwise: if you absolutely need riverctl spawn, you need to make sure the env is present when river starts (again, typically a wrapper script)

17:22 <tiosgz> if you don't need riverctl spawn, you can run the stuff directly (just append `&` to have it in the background), in which case the env is needed where you run the stuff

17:22 <tiosgz> also, i don't think shell functions ever get exported

18:37 <kztx> Why does `riverctl spawn` exist?

20:53 <ifreund> I guess so you can bind keys in river to run shell commands

22:51 <Cornelius-Figgle> to open apps???