<leon-p>
ifreund: btw, what do you think of additionally dumping warn and err messages to syslog? makes it possible to get at least some info on what went wrong when river weirds out and you are not logging it actively
<leon-p>
I used that recently to find out that river was OOMing on me, for example
<ifreund>
leon-p: I'd be happy for river to log warn and higher to syslog as well by default. Let's also add a -no-syslog option though
<leon-p>
sure!
<ifreund>
also, river was OOMing on you? did you disable overcommit or something?
<novakane>
hmm that the if condition just above that is never true instead it seems
<novakane>
Why dos this stop to be true after the zig update though, I have no idea
<novakane>
s/dos/did
<ifreund>
novakane: it's likely a compiler bug, I'd try restructuring the code to put as much as possible on separate lines and see if that changes anything
<ifreund>
if it does, submit an upstream zig bug report
<novakane>
ifreund: it is `seat_node.data.focused.view == &self` that is false now
<ifreund>
novakane: oh I see the problem
<tleydxdy[m]>
hmm have anyone set up zig 0.10 on arch?
<leon-p>
ifreund: it was OOMing because my workstation shares memory between CPU and GPU. So when I was doing something graphically intensive (some python image processing library), something went wrong
waleee has joined #river
smach has joined #river
<fleischie>
/quit
<fleischie>
Whoops. :O
talismanick has joined #river
talismanick has quit [Ping timeout: 252 seconds]
talismanick has joined #river
<talismanick>
I haven't used Zig before, but I have used C and C++. Not at all familiar with the details of wlroots or Wayland itself. If I wanted to help along the tablet-v2 bindings (so I could use my pen), where should I begin?