01:01 <daurnimator> ifreund: any word on a zig 0.11 compatible release?

06:42 <leon-p> I think I just managed to bug out pointer maps, but i have no idea how

06:42 <leon-p> maybe related to virtual pointer

10:57 <ifreund> daurnimator: 0.3.0 is still a while out, I guess an 0.2.5 that's zig 0.11.0 compatible wouldn't be too much effort on my end

11:02 <waleee> wlroots 0.17 looks like the big hurdle with that changelog

11:03 <ifreund> wlroots 0.17 won't be that bad, just busy work mostly that unlocks better wlroots features and bugfixes

11:03 <ifreund> the most time consuming part of river 0.3.0 will be fixing the remaining bugs and implementing the couple of features I added to the 0.3.0 milestone

11:22 <daurnimator> ifreund: move them to 0.4.0?

11:22 <ifreund> daurnimator: nope

11:22 <ifreund> I'll tag a 0.2.5 shortly for you

11:24 <leon-p> ifreund: would you be opposed to merge an impl of ext-foreign-toplevel-list in 0.3.0 since I did not have the time to get that into wlroots 0.17?

11:25 <leon-p> basically I want unique view IDs

11:50 <plusgut> hi everyone, i would like to configure server-side-decorations, but neither in the manpage for riverctl nor in the protocols directory am i able to find something to that topic. the only thing i was able to find was a closed pr about view-management

11:51 <plusgut> i would like to configure river in a way, that i have a view-container with tabs, which holds the windows. is that a thing that river is able to do?

12:25 <novakane> plusgut: for ssd, which version of river are you using?

12:28 <novakane> for 0.2.4 look for csd-filter-add in riverctl(1) man page and for the master branch look at the Rules section

12:47 <daurnimator> ifreund: thanks :)

12:48 <daurnimator> ifreund: to be annoying, we'd also love a wlroots update :)

12:55 <ifreund> daurnimator: wlroots update will probably have to wait for 0.3.0 unfortunately, it's a lot more work to backport

12:55 <ifreund> hopefully that's more manageable than dealing with old zig dependencies, wlroots is a much lighter weight dependency

12:56 <ifreund> I haven't even updated river master to 0.17.0 yet, that's pretty much next on my todo list

12:56 <daurnimator> ifreund: luckily you're not the last person on the wlroots 0.16 train. https://archlinux.org/packages/extra/x86_64/wlroots0.16/

12:57 <ifreund> true :)

13:08 <ifreund> leon-p: RE ext-toplevel-list, I'd like to see the wlroots patch landed in master branch before considering a river implementation to tide us over till wlroots 0.18.0

13:09 <ifreund> there's been talk of a shorter wlroots release cycle as well fwiw.

13:10 <ifreund> the goal has been ~2 releases a year for a while (though 0.17 took much longer than that) but upstream might move towards 3-4 releases per year

13:18 <p00f> are there only 9 tags or more?

13:18 <p00f> the manpage only has examples of 9

13:18 <p00f> but riverctl set-focused-tags $((1 << 10)) doesn't fail as such

13:19 <ifreund> p00f: there are 32

13:20 <p00f> ah thanks

13:20 <ifreund> If we didn't document that anywhere... whoops

13:44 <plusgut> novakane thanks for the hint, i'll have a look into that

16:34 <p00f> ifreund: does 0.2.5 reverse rule-add, back to float-filter-add?

16:49 <novakane> p00f: well revert no since rule-add wasn't in 0.2.4 iirc, and 0.2.5 only update to works with zig 0.11 so there is no new features from the master branch

16:56 <p00f> I don't understand wtf I installed then 👍

16:57 <p00f> archlinux's 0.2.4-2 has rule-add

16:58 <p00f> test

17:02 <leon-p> sounds like a packaging mistake then 🤷

17:28 <ifreund> p00f: 0.2.5 is exactly the same functionality as 0.2.4

17:28 <ifreund> 0.3.0 will add rule-add and more, but has not been released yet and will take at least another month

17:29 <ifreund> I only made an 0.2.5 release because the arch packagers asked for a release with zig 0.11 compatibility

17:54 <novakane> well river 0.2.4 on arch was actually river latest commit on master a few hours ago so yeah...

18:12 <ifreund> Ah, hope it wasnt like that for too long

18:31 <p00f> novakane: but the old "0.2.4" didn't have #922

18:36 <p00f> oh understood

18:41 <p00f> wait, this means #922 has been fixed on master since I didn't have it on arch's 0.2.4

20:00 <tiosgz> p00f: nope, #922 never existed on master. it has been introduced in the 0.2 update to zig 0.11, apparently because ifreund has typed one more `!` than needed

20:10 <p00f> i see