Nosrep has quit [Remote host closed the connection]
Szadek has quit [Ping timeout: 256 seconds]
waleee has quit [Ping timeout: 246 seconds]
waleee has joined #river
jao has quit [Ping timeout: 260 seconds]
waleee has quit [Ping timeout: 256 seconds]
waleee has joined #river
waleee has quit [Ping timeout: 264 seconds]
waleee has joined #river
eShaev9z_ has joined #river
eShaev9z has quit [Ping timeout: 246 seconds]
notzmv has quit [Ping timeout: 264 seconds]
notzmv has joined #river
waleee has quit [Ping timeout: 256 seconds]
waleee has joined #river
waleee has quit [Ping timeout: 252 seconds]
notzmv has quit [Ping timeout: 255 seconds]
waleee has joined #river
waleee has quit [Ping timeout: 256 seconds]
waleee has joined #river
Misthios has quit [Quit: Misthios]
Misthios has joined #river
waleee has quit [Ping timeout: 265 seconds]
waleee has joined #river
waleee has quit [Ping timeout: 255 seconds]
vyivel has quit [Ping timeout: 255 seconds]
vyivel has joined #river
alexherbo2 has joined #river
jao has joined #river
alexherbo2 has quit [Remote host closed the connection]
alexherbo2 has joined #river
alexherbo2 has quit [Remote host closed the connection]
alexherbo2 has joined #river
hryx has quit [Ping timeout: 260 seconds]
<leon-p>
hmm... firefox with active video playback on a non-active tag kinda kills our performance on all outputs, there is obverseable micros-stutter in cursor movement. If the tag is activated and the view shown, everything is fluid again.
<novakane>
leon-p: I don't seem to have this problem, I can't see any stutter
<lordmzte>
absolute WL beginner here, how would i get the amount of monitors used in the current river session in zig?
<lordmzte>
i assume zig-wayland can help with that?
<novakane>
lordmzte: I don't think there is something to get the number of output, I would probably use the length of the list you use to store output struct
<lordmzte>
output struct? :D
<novakane>
or just a variable that update the number when there is a new wl_output event if you don't need everything else
<novakane>
it is store in a std.TailQueue(Output), so you could just use the length that what I'm talking about
<novakane>
you'll need some basic understanding on how Wayland events/request works though
alexherbo2 has quit [Remote host closed the connection]
alexherbo2 has joined #river
hryx has joined #river
<novakane>
ifreund: about waylock, didn't knnow about mlock that's nice, per the man page it says that you should not use fork() after it, isn't that what you do?
<novakane>
I could have miss something though
waleee has joined #river
<leon-p>
interestingly the fork thing is only mentioned in mlock.2, not mlock.3p. I wonder if this is a linux limitation or an oversight in the POSIX manual
<novakane>
oh, right, haven't check the posix man page, good question
alexherbo2 has quit [Remote host closed the connection]
alexherbo2 has joined #river
<ifreund>
POSIX may leave it undefined or unclear
<ifreund>
anyhow yeah I should definitely change the code to only call mlock after fork, good catch novakane
<ifreund>
FreeBSD has the same behavior as Linux at a glance
<novakane>
np, it's probably better to change it yeah, better safe than sorry
groknull has joined #river
groknull has quit [Remote host closed the connection]
groknull has joined #river
groknull has quit [Remote host closed the connection]
<mx08>
leon-p: did you get my PM?
groknull has joined #river
groknull has quit [Remote host closed the connection]