01:48 <NickH> IIRC there have been quite a few people using river 0.1.1 trying to use the init from the repo head.

01:49 <NickH> Not sure if they were on void... does the void package not ship with an example init?

01:55 <scrollmaster> NickH: void should have the example init in /usr/share/examples according to the package manager, though I don't personally use the river package

01:59 <NickH> Hmm, wonder why these people are grabbing the init directly from github.

02:00 <scrollmaster> most users probably expect there to be a default config in /etc instead of /usr/share, but I'm not sure

02:02 <NickH> On Debian most users should expect to find example config files under /usr/share/doc/<packagename>/

02:09 <scrollmaster> oh all right. Does Debian usually have default system-wide configs for its packages as well or just the example configs?

02:12 <NickH> Services generally come with sane default configs modified from upstream by package maintainer.

02:12 <NickH> User stuff usually doesn't.

02:12 <NickH> But *every* package has a /usr/share/doc/<packagename>/ directory.

02:13 <scrollmaster> yep, that makes sense

02:13 <NickH> It's the first place I always look after installing something.

02:15 <scrollmaster> on void, I usually check /etc/, /usr/share/examples/, and /usr/share/doc/. Afaic, it's dependent upon the package/maintainer, but I haven't gotten into packaging anything quite just yet

02:17 <scrollmaster> so that might be a source of confusion for new users, but it's usually easy to find with void's package manager

02:18 <scrollmaster> s/Afaic/Afaict/

11:43 <makaba> novakane: do you know any method to "monitor" which layout it's in use trough rivercarro? I'd like to make an indicator on waybar.

11:55 <novakane> makaba: rivercarro send a name to river for each layout https://git.sr.ht/~novakane/rivercarro/tree/main/item/src/main.zig#L415-420

11:55 <novakane> I'm not sure how do you get this info from river right now though

11:56 <novakane> ifreund or leon-p could probably better tell you

13:08 <leon-p> I don't think you can query the name of the active layout right now

13:08 <leon-p> novakane makaba ^

13:11 <novakane> ah yeah that what I thought, I didn't remember anything related to this in river code

14:56 <snakedye> river-toplevel-v1 is in limbo

15:28 <leon-p> where "limbo" means: I threw an idea into the room but am no longer sure if it is a good idea and don't really have the time to pursue it anyway

19:48 <maxvv> Hi everyone! I've recently switched to river from sway and one thing I really missed was swaybar, and so I'm happy to announce my port of i3bar - https://github.com/MaxVerevkin/i3bar-river. It's not fully compatible with the protocol yet, but it's WIP. Bug reports (if your favorite status command doesn't work it's a bug) are very appreciated.

20:36 <leon-p> maxvv: nice project! If you like, you can add your bar to the recommend software on the github wiki!

20:38 <leon-p> If you allow me one small recommendation: It would be cool if the river support was optional. There are a lot of compositors right now that are lacking desktop widgets such as a nice bar and making something universal would be great for them too.

20:55 <maxvv> Thanks, I'll add it to the wiki. I will try to make the river integration optional once I manage to fully implement the i3bar protocol (contributors are welcome btw).