10:09 <novakane> damn, can't build river with zig 0.11 with an error not really useful to me https://paste.sr.ht/~novakane/b4271b0730b225fd75cdaf7814fbf863f2ba7619

10:14 <ifreund> novakane: I'm working on fixing it, it's an upstream zig issue

10:15 <ifreund> specifically a crash when trying to print a compile error

10:16 <novakane> ifreund: oh okay, is there an open issue about this? I couldn't find anything

10:17 <ifreund> I think its related to https://github.com/ziglang/zig/issues/16746

10:17 <ifreund> It might be slightly different though, and might already be fixed on zig master by https://github.com/ziglang/zig/issues/16746

10:17 <ifreund> (currently waiting for zig master to build)

10:18 <novakane> btw do you mind pushing zig-wayland next-zig branch to master once it's done without waiting for river to be updated, like last time, no rush though

10:19 <ifreund> novakane: there are still issues with the server side code in zig wayland, for example this compile error that's crashing the zig compiler

10:19 <ifreund> also I wanted to take another stab at simplifying the build.zig API

10:21 <novakane> ifreund: np, it's ready when it's ready, tha's more about not waiting on river, I'll wait till it's good though

10:23 <novakane> I didn't have any problem to compile zig-wayland though, do it doesn't always crash?

10:23 <ifreund> it only crashes if one causes the server side FooV1.setHandler() function to be semantically analyzed

10:24 <ifreund> tinywl.zig compiles just fine for example, but river doesn't yet

10:27 <novakane> allright, seems like I still have the same problem with a zig master tarball for zig website

10:30 <novakane> welp I let you works on that, zig debug build seems way more useful for log than what I can get lol

10:32 <ifreund> yeah, a debug zig and --debug-compile-error is pretty necessary for this kind of thing

11:17 <ifreund> well, I've fixed the compile error and opened https://github.com/ziglang/zig/issues/16750

11:18 <ifreund> now the zig upgrade is only blocked on the potential build system improvements

11:50 <novakane> nice! you fixed it on river side or we will need to wait for zig 0.11.1?

11:53 <ifreund> novakane: it was an error in reporting a compile error, fixing the compile error avoids the bug entirely

11:56 <novakane> ifreund: cool, if you push to the next-zig branch maybe I could play a bit with the CI to see if the problem with musl 1.2.4 is fixed

17:33 <Guest15> Is there any way to set the state of fullscreen instead of toggle it, apart from using a custom layout generator? Or is there any way to tell if the current window is in fullscreen or not, so you can either toggle or not toggle accordingly?

17:33 <Guest15> I was thinking of writing a wrapper around toggle-fullscreen that records the state per-tag in a temporary file, if there is no built-in method. I'm pretty there isn't based on the documentation, IRC logs, and GitHub issues I've looked at, but I thought it was worth asking just in case.

17:44 <Guest15> Never mind, I'll just implement the wrapper I mentioned