00:00 <leon-p> a wrapper script is over-complicating it a bit I think. Anyway, functions you define in a script can't be called in another if you merely execute it. YOu have to source the script with the definitions, but again that is really over-complicating it

00:00 <Pound_Hash> Well, I have a lot of configurations to do

00:02 <leon-p> sure, then create a script with the function definitions. But using that as a "wrapper" will not work. function definitions are not shared to children like env vars are. You'll have to source that script, treat it like a library

00:02 <Pound_Hash> So my setup is: in `/etc/profile.d/` I have three scripts. One to determine time of day and set several environment variables. It also sources two other scripts depending on the time, one script called `light` and another called `dark`

00:02 <Pound_Hash> These are all in /etc/profile.d

00:03 <Pound_Hash> In the `light` and `dark` scripts, I define the specific environment variables for the respective times of day

00:04 <Pound_Hash> Finally, river runs and loads init. In the init, I have it run the `riverctl` commands

00:05 <leon-p> so instead of doing the profile thing with scripts containing functions, why not just turn the functions into scripts and plop them into your bin/ ?

00:05 <Pound_Hash> I only have one function

00:06 <Pound_Hash> The scripts are only setting environment variables, with the exception of running one `sed` command (for kakoune's config) and lastly this issue with river's colors

00:08 <leon-p> so what exactly is the thing that is "not working" then?

00:08 <Pound_Hash> If I define this one function in a script loaded by pam in profile.d/ , then should I try exporting it? Or should I `source` it?

00:08 <Pound_Hash> The one thing that isn't working is setting river's colors via rivertctl

00:09 <leon-p> are your sure whatever calls your riverctl colour script has WAYLAND_DISPLAY in its env?

00:09 <Pound_Hash> I can put the commands in a variable and run eval

00:09 <Pound_Hash> But that's not secure

00:09 <Pound_Hash> I want to get in the habit of writing good code

00:10 <Pound_Hash> River's init calls the function (or runs the eval)

00:10 <Pound_Hash> The functions/variables have already been defined in previously run scripts (those run by pam)

00:11 <leon-p> my best advice would be to first reduce the complexity of your setup a bit. don't export functions, just write callable scripts

00:11 <Pound_Hash> Okay

00:12 <Pound_Hash> I'll try

00:12 <Pound_Hash> Thanks

09:30 <chismoso> installed on voidlinux. opens with coloured background and a cursor. no key strokes working. already placed init to /.config/river and made it executable.

09:39 <ifreund> chismoso: the correct path is ~/.config/river/init

09:39 <ifreund> or $XDG_CONFIG_HOME/river/init

09:45 <chismoso> yes. init file is in ~/.config/river

10:03 <ifreund> chipps: and what is in that init file?

11:43 <novakane> also if this is from the void repo package, don't use the init example from the master branch

12:32 <ane> interesting, for some reason gcr-prompter, the GUI prompter doesn't start on river when using gnome-keyring as the ssh agent

12:32 <ane> on sway it works just fine, the gui prompt appears, but on river it just fails

12:33 <ane> i.e. doing ssh blah on sway brings up a graphical passphrase prompt; on river nothing appears and the signing fails

12:33 <ane> I checked the output of "env" and there isn't anything obvious there ... both wm's execute the eval + export thing

12:40 <ane> aha, "gcr-prompter[12731]: cannot open display:"

12:40 <ane> wtf is that

12:44 <ane> ok wtf doing "dbus-update-activation-environment --systemd WAYLAND_DISPLAY" fixes this

13:13 <ane> aha! fedora is fixing this by installing https://github.com/alebastr/sway-systemd

13:54 <ifreund> ew

14:02 <n0r> Do windows know if they are hidden or shown?

14:09 <ifreund> n0r: not really. If they're hidden river will stop sending them frame callbacks though to avoid pointless rendering

14:27 <NikhilSingh[m]1> suggest any calender application CLI one will do the job too.

14:28 <tleydxdy[m]> cal

17:14 <DZoidberg_> I have a small question about river. Is there are equivalent to sways `assign` command?

17:14 <DZoidberg_> for riverctl

17:14 <DZoidberg_> Or do you this with a custom client which interacts with some river wayland protocols

17:46 <n0r> Chromium is on tag c and when I switch to it, chromium seemed to be aware of the pressed c. So I tested with wev, opened it in tag w, held down super and pressed w a few times. Wev repeatedly noticed me releasing w, but not pressing w. (Super w is mapped to setting focused tags to tag w of course). This is weird and in the case of chromium annoying. Can I change that? Does this mean I messed up my mappings?

18:03 <tleydxdy[m]> how did you bind the keys

18:03 <tleydxdy[m]> also are you building from master?

18:04 <n0r> No, river 0.1.3

18:05 <n0r> tag=1

18:05 <tleydxdy[m]> yeah use master

18:05 <n0r> for key in A B C D E F G H I J K L M N O P Q R S T U V W X Y Z

18:05 <tleydxdy[m]> that release is super outdated

18:05 <n0r> riverctl map normal Mod4 "$key" set-focused-tags $tag

18:06 <n0r> I am way to dumb to compile stuff myself.

18:06 <tleydxdy[m]> river is not very bad

18:07 <tleydxdy[m]> take a look at the readme,

18:11 <n0r> Yeah that assumes a ton of knowledge I really don't have. Also not sure how that would work for me at all since I'm on NixOS which handles installed software very differently.

18:12 <tleydxdy[m]> nixos, cool, you should be able to edit it off their script ig

18:12 <tleydxdy[m]> just tell it not to get the tag

18:14 <n0r> Not sure how to do that. I'll look into that when I got time, at least now I know this is different in master.

18:19 <n0r> Btw why have releases if everyone is expected to build master ;)

18:20 <tleydxdy[m]> yeah big-releases controll the software industry, sadly

18:36 <novakane> DZoidberg_: there is no equivalent in river and you can't do this in an other client

18:46 <DZoidberg_> ok

18:46 <DZoidberg_> maybe ill try to contribute that as a feature to river.

18:47 <DZoidberg_> thanks for your response

20:53 <ifreund> n0r: yeah it's been waaay too long since the last river release, I've been waiting on wlroots 0.16.0 but I expected that to release a month or 2 ago :/

21:00 <alebastr> ifreund: river master still uses wlroots 0.15, right? Have you considered making another release before updating to 0.16?

21:01 <ifreund> alebastr: I'd rather not, I'd like 0.2.0 to drop wlr-input-inhibit for ext-session-lock

21:02 <ifreund> which has been ready in wlroots master since like january

22:26 <Guest42> how can I setup fibonacci tiling layout without a layout generator