01:30 <talismanick> kennylevinsen: Sorry for going silent for a while there - somehow corrupted GRUB and took a while to figure it out

01:31 <talismanick> would the command I want in config.toml be "cage -s -- tuigreet --cmd bash -l river "?

01:31 <talismanick> or 'bash -l river' singlequoted, perhaps?

01:38 <talismanick> Going to try again with the above and the arg to --cmd single-quoted. Wish me luck.

01:44 <talismanick> welp, once more locked out

01:45 <talismanick> I saw a brief message in red about some .c file, then black

02:01 <talismanick> What is the --cmd I want to use to launch river?

02:01 <talismanick> with my bash_profile loaded

02:01 <talismanick> I can't figure it out ;_;

05:13 <kennylevinsen> talismanick: just don't use bash_profile, use .profile or a wrapper script around river

05:14 <kennylevinsen> .bash_profile is for when you log into bash, which is not what you're doing

12:45 <amirography> Hey all! Quick question, in the example configuration, the shell script exec the rivertile. Is it just to tell the os that we are finished with the script or does it do anything else?

12:48 <novakane> the question is about rivertile or exec?

12:50 <amirography> Mostly the reason for exec at the end of init.

12:51 <amirography> I'm doing a config in go lang and i want to know if i can start rivertile earlier concurrently.

12:55 <novakane> well you can't have anything after exec in a script, although you're not obligated to launch rivertile like that, I launch mine with a run it service, still at the end of the init though

12:57 <amirography> I see. Awesome! Thanks for your answer!

15:27 <ifreund> I should probably remove that exec, it's done nothing but confuse people xD

16:26 <icp> Not technically a river question but does anyone know of a simple alternative like wlopm that's available in the void repo?

16:37 <ifreund> icp: not that I know of, compiling wlopm from source is straightforward though and it wouldn't be hard to package it yourself it you were so inclined

16:38 <icp> thanks I'll try compiling, I'm trying to get idle management set up with swayidle

16:39 <leon-p> icp: let me know if you have any trouble with wlopm; It should be fairly portable, but maybe I missed something

16:41 <icp> make is telling me I need wayland-scanner which leads to to https://github.com/void-linux/void-packages/blob/master/srcpkgs/wayland-scanner++

16:41 <icp> So is that a build dep?

16:42 <ifreund> icp: yes, and the one you want is part of wayland-devel on void

16:42 <ifreund> wayland-scanner++ is presumably something C++ related and not what you need

16:48 <icp> wlr-output-power-management-unstable-v1.c:1: error: ISO C forbids an empty translation unit [-Werror=pedantic]

16:48 <icp> cc is provided by gcc-10.2.1pre1_3 (I think)

16:50 <leon-p> the translation unit should not be empty, are you sure wayland-scanner is working?

16:52 <icp> How do I check that? wayland-scanner -v outputs wayland-scanner 1.20.0

16:52 <leon-p> the empty file may be leftover from when you tried `make` without wayland-scanner installed and make now did not bother to generate it again.

16:53 <leon-p> try a clean build: `make clean; make`

16:54 <icp> yeah I rm -rf ed that git dir and recloned and make again which worked :p

16:55 <icp> well thank you for the help and the river set up guide in your blog, which helped immensely

16:55 <leon-p> glad it helped you

16:58 <ifreund> make's caching is kinda dumb :/

16:58 <ifreund> iirc it's based purely on file timestamp

16:59 <icp> If I may request one small feature to help new people onboarding river, please make the example config available in the river repo somewhere in the local river install. So that one can just do for example cp /etc/river/example ~/.config/river/ini. It was such a pain to set it up initially, especially since void was one version behind the master so

16:59 <icp> the raw git master link didn't work

17:07 <ifreund> icp: I think that's more of a feature request for the void package, which I'd be happy to oblidge

17:07 <ifreund> I don't think there is a standard place to install examples to, so my decision was to not have the build.zig install it but instead rely on distros which do have a standard examples location to handle that.

17:08 <ifreund> I guess we could use a PACKAGING.md targeted at distro maintainers too

17:12 <novakane> can't hurt to have this

17:13 <novakane> "packaging.md: void: update to llvm13 then update to llvm14" :P

17:14 <icp> haha right, stuck on river 0.1.1 while seems like 0.1.4 is on the horizon

17:15 <ifreund> void's llvm packaging has been truely glacial this time

17:16 <ifreund> it looks like someone competent is pushing directly for llvm14 and leaving bits of llvm12 around for zig

17:17 <ifreund> if that gets merged then I can probably deal with getting the llvm12 bits replaced with llvm13 bits so we can finally have zig 0.9

17:17 <ifreund> packaging llvm is a pain, but not as much of a pain as all the other crap that depends on llvm :D

17:18 <icp> also rust 1.60 has been blocked for a fairly long time

17:18 <novakane> I mean packaging llvm13 now would kinda be useless

17:19 <ifreund> novakane: zig isn't compatible with llvm 14 yet

17:21 <novakane> sure but the I mean for void, the time the PR is merged we'll probably be close to llvm14 and a new zig release

17:22 <ifreund> don't expect zig 0.10 for a couple months still

17:22 <novakane> yeah I saw that this release will take some time

17:22 <ifreund> we're planning on shipping the self hosted compiler with 0.10 and there's still a good bit of work to do

17:23 <novakane> still prefer to directly have llvm14 :P

17:53 <ringo_> Hello there!

17:59 <novakane> o/

17:59 <ringo_> I pasted the section about sticky tags from the wiki into my init file and now every new window spawns as sticky

18:00 <ringo_> Did I do something wrong? Is that the default behavior? Either way I don't know how to fix it ^^

18:03 <novakane> oh, never saw that sticky section, that doesn't sound like a default behavior though

18:06 <novakane> hm quickly reading this, I don't see why new windows would spawn on the sticky tag

18:07 <ringo_> I have Mod + D to launch wofi maybe I hit S by accident at the same time

18:13 <ringo_> Nope that wasn't it

18:14 <ringo_> Do you think the part with sticky is supposed to replace the normal tags management part from the init? Or is it an addition, like I did?

18:17 <tleydxdy[m]> there's a bug where if the monitor turn off or go to sleep it will loose the spawn tagmask

18:18 <tleydxdy[m]> just re run the line that sets spawn tagmask should fix it

18:20 <ringo_> Ahhh well that explains it. I start my laptop with the screen off and monitor disconnected. Then I connect my external monitor once fully booted. Otherwise I have this weird firefox bug where it's running, there's a window border but it's completely invisible

18:22 <ringo_> It was like that on Sway as well

18:22 <tleydxdy[m]> Firefox is weird

18:23 <ringo_> It's like because I boot up with a dual monitor setup, it doesn't know where to draw the window

18:24 <ringo_> And it's not 100% of the time mind you

18:24 <ringo_> Starting firefox from the console doesn't give me any error code either when it happens

18:24 <ringo_> If I plug in the monitor after being booted up then it never happens

18:36 <novakane> everybody here have different bug with Firefox, they're personalized :P

18:38 <ringo_> XD