02:10 <ifreund> novakane: nope, I hate it xD

02:10 <ifreund> I have no idea why but libway

02:10 <ifreund> libwayland refuses to build on the CI

02:13 <ifreund> I also don't like bach

02:13 <ifreund> s/bach/bash/, I do like bach

02:14 <ifreund> anyhow, when I finish that I'll tag 0.1.1 for the wlroots update and start on 0.1.2 for the zig update

05:35 <ifreund> river 0.1.1 is now ready in theory, just going to give it a day or two for bug reports to trickle in

07:53 <leon-p> ifreund: btw, how does your lock protocol work wrt to scaling? It is a protocol error to submit a buffer with a size that does not match the size of the configure event. I assume this will also respect the buffer scale (when configure event is 500x500 on a scale 2 output, the buffer could be either 500x500 with scale 1 or 1000x1000 with scale 2). However since this is (to my knowledge) the first surface role that actually enforces a specific windo

07:53 <leon-p> w size it might be good to explicitly mention this

07:54 <leon-p> s/window/buffer/

08:54 <novakane> ifreund: so what's your setup on void to get wayland/wlroots up to date for river?

08:56 <novakane> I've got like 20 emails `ci: update to wlroots 0.15` xD

12:53 <Fr0stBit> ifreund: Hi!

16:07 <ifreund> novakane: I built/installed wayland 1.20.0 through xbps-src and build wlroots from source installing to ~/.local just like always

16:08 <ifreund> the CI stuff was because for some unknown reason wayland failed to build if built as a meson subproject

16:08 <ifreund> so I gave up on that and just built/installed it separately

16:21 <ifreund> leon-p: " The size of a surface (and relative positions on it) is described in surface-local coordinates, which may differ from the buffer coordinates of the pixel content, in case a buffer_transform or a buffer_scale is used.

16:21 <ifreund> from the descrption of wl_surface in wayland.xml

16:21 <ifreund> does that clear things up?

16:23 <ifreund> see also the description of the attach request

16:38 <novakane> ifreund: no other problem than the firefox one with wayland? Does you need a special flag to build river with wlroots or you don't have the xbps package installed?

16:40 <ifreund> the firefox wayland 1.20 BS is only an issue if building firefox from source

16:40 <ifreund> I don't follow the second half of the question really...

16:41 <Phyrric> I just have firefox from the void repos without any modification

16:42 <novakane> I mean do you have wlroots build from source and wlroots from xbps and if so is there a flag to zig to tell wich one to use

16:43 <novakane> hope it's more clear

16:43 <novakane> Phyrric: yes because wayland is not up to date in the void repo

16:52 <ifreund> novakane: you probably need to set those environment variables to tell pkg-config, ld, etc to look in ~/.local first

16:52 <ifreund> pretty sure I have a wlroots package installed as well

16:53 <ifreund> novakane: https://github.com/ifreund/dotfiles/blob/daf4c8ef0eebb444754c6adeea9ce2c525c70b65/zprofile#L12-L15

16:54 <novakane> ifreund: yeah I already have all of this set

16:55 <ifreund> so what problem are you having?

16:55 <novakane> well river doesn't use the wlroots version in ~/.local

16:56 <novakane> hmm wait I think the pkgconfig file from wlroots is not in ~/.local

16:57 <ifreund> I have ~/.local/lib/pkgconfig/wlroots.pc

16:59 <novakane> ah yeah my bad I was looking at ~/.local/share/pkgconfig like river but I do have it in ~/.local/lib

17:00 <novakane> so that's not the problem I guess

17:04 <novakane> hmm yeah ` pkg-config --modversion wlroots` return 0.15.0 though I have a compile error `@compileError("zig-wlroots requires wlroots version 0.15");`

17:16 <novakane> ifreund: any special flags when you build wlroots?

17:17 <ifreund> nope

17:17 <ifreund> just meson build --prefix ~/.local then ninja -C build install

17:18 <novakane> well I have no idea why it doesn't works then :/

17:36 <ifreund> novakane: could you paste the full output that zig's giving you? It should show exactly what directory it is looking in for wlroots headers

17:38 <novakane> ifreund: https://paste.sr.ht/~novakane/6b56d59e712f8290e3400452db6c57e672e33423

17:59 <ifreund> novakane: I don't see a -I ~/.local/include there

18:04 <novakane> ifreund: though https://git.sr.ht/~novakane/dotfiles/tree/main/item/.config/zsh/.zprofile#L73

18:06 <ifreund> novakane: try unsetting that

18:09 <novakane> ifreund: huh it worked, why unsetting it make it found it

18:10 <ifreund> I don't think zig looks at C_INCLUDE_PATH but pkg-config does apparently and assumes that the compiler does as well

18:10 <ifreund> which means pkg-config omits the -I ~/.local/include if you have it set

18:17 <novakane> hmm well kinda annoying

18:18 <novakane> how does you don't have this errors though?

18:23 <ifreund> I really don't know xD

18:43 <novakane> it really doesn't make any sense, black magic lmao

18:44 <novakane> well thanks for the fix anyway

18:48 <ifreund> no problem

19:43 <ifreund> novakane: I don't actually recall why I had C_INCLUDE_PATH set by the way, getting rid of that doesn't seem to make anything break

20:00 <novakane> ifreund: I don't remember either tbh

20:02 <novakane> I'm not sure if I needed to use for gcc one day, maybe kakoune? I don't know

20:21 <Nulo> Is there any way to make windows (ideally only some that meet a criteria) go on a lower opacity when unfocused?

20:22 <leon-p> there was, but it got removed again :P

20:24 <ifreund> Nulo: I intend to expose a way to set opacity again eventually, but it might take a year or so

20:24 <ifreund> not because it's that complex to implement, but because other stuff is higher priority

20:25 <ifreund> anyone know of anything that should block 0.1.1? I'll probably tag it in the next hour or two

20:25 <Nulo> Good to know, thanks

21:02 <novakane> ifreund: nothing for me, everything working fine now

21:03 <novakane> well paper from snakedye doesn't works anymore but that's not river fault ^^

21:03 <snakedye> I need to rewrite it. Snui's API radically changed since I wrote it

21:10 <novakane> I can imagine, with what you showed us about snui

21:37 <tiosgz_> ifreund: didn't you forget to also modify the code in Cursor.zig (not only remove the comment)?

21:38 <tiosgz_> re https://github.com/riverwm/river/commit/6a093fecee3a8734b38343a9335faf8ab00b02d5#diff-4c3c7cdc3edbc685554073846f1c70e44519f2f59e8a51cc05f57a56eb41544c

21:38 <ifreund> tiosgz_: actually no, that comment was wrong

21:38 <tiosgz_> ah

21:38 <ifreund> well it was correct about the wlroots change but wrong that that wlroots change meant that river's code should be changed there

21:50 <novakane> ifreund: talking about release, how did you manage the tarball with submodule, I know you talked about it at the time of the first release but I don't remember

21:51 <novakane> because sr.ht made a tarball when I tagged rivercarro but obviously it doesn't works, and even if I don't really care about this I don't really like having this broken tarball

21:52 <ifreund> novakane: I actually just took the time to make a script for that: https://github.com/ifreund/dotfiles/blob/macair/local/bin/tarball.sh

21:52 <ifreund> just run e.g. `tarball.sh river-0.1.1` in the root of the repo

21:54 <ifreund> don't put spaces in the name or it will probably break xD

21:54 <novakane> ifreund: oh that's nice, thank you, probably be really useful till zig get a package manager

21:54 <ifreund> enjoy :)

21:55 <novakane> space in a filename? I'm not a window user huh :P

22:21 <ifreund> 0.1.1 is released :)

22:21 <ifreund> now time to finish the zig 0.9.0 upadate and do another release xD

22:22 <ifreund> this is good, I'll get my release process nice and polished

22:30 <novakane> nice one release by week that's great :P

22:31 <novakane> isn't zig 0.9.0 branch kinda finished?

22:32 <ifreund> yeah, I think so

22:33 <ifreund> might have some rebasing to do now

22:34 <leon-p> IIRC we also wanted to refactor a few things with the new saturating arithmetics, but I can't remember where

22:34 <ifreund> oh yeah, that would be nice to do

22:35 <ifreund> one place is cursor resize/move handling

22:35 <novakane> yeah probably, cool that you think about rebasing, you're improving :P

22:35 <novakane> need to merge a PR in zig-pixman too

22:39 <ifreund> heh