00:08 <sewn> inkflaw: riverctl for river compositor management

00:08 <sewn> not for display management

00:08 <sewn> use wlopm

01:00 <ahmadraniri> Hello, if we don't run any layout manager (e.g. rivertile), so river behave like regular floating window compositor, Am I right ?

04:02 <inkflaw> > Hello, if we don't run any layout manager (e.g. rivertile), so river behave like regular floating window compositor, Am I right ?

04:02 <inkflaw> Please check https://codeberg.org/river/wiki#my-windows-are-not-tiled

04:03 <inkflaw> @ahmadraniri Please check https://codeberg.org/river/wiki#my-windows-are-not-tiled

04:04 <inkflaw> sewn: Thank you so mach, it's working, and I also find https://github.com/lilydjwg/dpms-off it's working also

04:05 <inkflaw> ahmadraniri: Please check https://codeberg.org/river/wiki#my-windows-are-not-tiled

13:11 <NemoGuest48> Hello! I have a problem...

13:11 <NemoGuest48> I'm definitely missing something, but my knowledge is limited here.

13:11 <NemoGuest48> I have a binary at $HOME/.local/bin/, specifically 'librewolf'. No matter how I try, I can't seem to execute it with 'riverctl spawn librewolf'.

13:11 <NemoGuest48> My main shell is fish and /bin/sh links to dash.

13:11 <NemoGuest48> What I tried:

13:11 <NemoGuest48> adding '$HOME/.local/bin' to $PATH in fish config (actually a default setting)

13:11 <NemoGuest48> adding '$HOME/.local/bin' to $PATH in .profile | /etc/profile

13:11 <NemoGuest48> adding 'PATH="$HOME/.local/bin/:$PATH"' to river/init

13:11 <NemoGuest48> creating dash config file through ENV and adding path there

13:11 <NemoGuest48> adding '$HOME/.local/bin' to $PATH in /etc/environment (and all other paths) [???]

13:11 <NemoGuest48> This kinda defies all linux laws, what am I missing?

13:13 <dnkl> you're missing how environment variables are inherited from parent to child processes, and how/by whom shell rc scripts are sourced

13:17 <NemoGuest48> dnkl It can explain all others, but I thought /etc/environment is absolute?

13:20 <dnkl> depends. for example, did you actually enter $HOME, like you wrote above? or the actual path? Don't think $HOME will work

13:23 <ifreund> NemoGuest48: technically nothing is absolute, /etc/environment is implemented as a PAM module which has to follow the same rules about environment inheritence as all other linux processes

13:23 <ifreund> I don't know anything about the syntax it supports though, I don't think it's executed by a shell

13:24 <ifreund> I personally set the environment variables I want set for my river session in a script that launches river

13:24 <dnkl> and I hope a pam module doesn't blindly expand environment variables...

13:26 <ifreund> I don't think it does, the pam_env(8) man page suggests that it only supports basic KEY=VALUE pairs

13:28 <dnkl> I would also suggest starting river from a try instead of through a graphical login manager. Much easier to verify the environment *before* river is started

13:28 <NemoGuest48> dnkl /etc/environment actually recognizes variables, for example 'ENV="$HOME/.dashrc"' works and "riverctl spawn 'foot -e /bin/sh'" recognizes that

13:29 <ifreund> on a more fundamental level, I don't think it makes logical sense to put user-specific config in /etc

13:30 <NemoGuest48> It definitely doesn't, I was just out of options

13:30 <ifreund> well, maybe try the option I suggested? (start river from a script that first sets up the proper environment)

13:30 <dnkl> redan the pam_env man page

13:30 <dnkl> Note that many environment variables that you would like to use may not be set by the time the module is called. For example, HOME is used below several times, but many PAM applications don't make it available by the time you need it.

13:31 <ifreund> I strongly believe that the simplest, most fool-proof way to setup the environment for your river session is to do so right before the river binary is run

13:32 <ifreund> pam_env seems like something that has no reason to exist

13:32 <ifreund> perhaps I'm missing something though

13:32 <NemoGuest48> I think I've tried that but I have problems with my memory so i'll try it again

13:41 <NemoGuest48> dnkl suggestion was correct, GDM was to blame, though I didn't expect it to eat /etc/environment

13:41 <NemoGuest48> Thank you, now 'export' in river/init works

13:42 <NemoGuest48> Though I still need to uproot gnome from my installation

15:45 <ifreund> tagged 0.3.5 with wlroots 0.18 support and gpu reset recovery :)

15:52 <dnkl> 🤘

15:52 <dnkl> (though I'm almost always on HEAD)

16:05 <ifreund> dnkl: HEAD will probably get a bit spicy when the the river-window-management-v1 protocol finally lands in master, be warned :)

16:53 <novakane> can't wait for when HEAD will breaks all layout generators at the same time :P

18:53 <leon-p> can't wait to finally deprecate *checks notes* 5 projects