waleee-cl has quit [Quit: Connection closed for inactivity]
travankor has joined #river
trav64757 has joined #river
trav64757 has quit [Remote host closed the connection]
trav86229 has joined #river
trav86229 has quit [Remote host closed the connection]
jjanzic has quit [*.net *.split]
ifreund_ has quit [*.net *.split]
voroskoi has quit [*.net *.split]
jjanzic has joined #river
voroskoi has joined #river
ifreund_ has joined #river
ifreund_ has quit [Ping timeout: 242 seconds]
voroskoi has quit [Ping timeout: 242 seconds]
samhsmith[m] has quit [Ping timeout: 244 seconds]
edrex has quit [Ping timeout: 240 seconds]
voroskoi has joined #river
ifreund_ has joined #river
samhsmith[m] has joined #river
edrex has joined #river
air69 has joined #river
air69 has quit [Client Quit]
ifreund has quit [Quit: WeeChat 3.0]
ifreund has joined #river
cmoi11 has joined #river
travankor has quit [Ping timeout: 268 seconds]
cmoi11 has quit [Read error: Connection reset by peer]
cmoi11 has joined #river
cmoi11 has quit [Read error: Connection reset by peer]
cmoi11 has joined #river
<cmoi11>
I'm trying to understand river-options. Where does the zriver struct come from? It's nowhere to find in the code...
<cmoi11>
Or I cannot find it :/
<ifreund>
cmoi11: It's generated from the protocol xml by zig-wayland in the build.zig
<ifreund>
you can find the generated code in zig-cache/zig-wayland
<ifreund>
and the protocol xml is in the protocol directory of course, I usually just read that
<ifreund>
note that river doesn't make very good use of the protocol yet, I plan to move all of the simple configuration options over to it eventually though (e.g. border width/color, padding)
<ifreund>
some are already moved in the open river-layout PR
<cmoi11>
Ok I think I'm beginning to understand this protocol thing. I've never looked into the wayland internals so far so maybe I need to check out this protocol think in general first...