<dnkl>
rscott: do you want 9 tags to be visible in the bar at all times, regardless of their occupied state?
Ordoviz has joined #river
Pound_Hash has quit [Quit: Pound_Hash]
jao has quit [Ping timeout: 252 seconds]
silv3r has joined #river
snakedye has joined #river
silv3r has quit [Quit: WeeChat 3.6]
hspak6 has quit [Read error: Connection reset by peer]
hspak6 has joined #river
n0r[m] has joined #river
fitrh has joined #river
n0r has left #river [#river]
smach has joined #river
groknull has joined #river
groknull has quit [Remote host closed the connection]
groknull has joined #river
groknull has quit [Remote host closed the connection]
jao has joined #river
<n0r[m]>
Some bars can show the focused tags, but it's not something I can get into a script, right? Needs to be a proper Wayland client or something like that?
n0r[m] has left #river [#river]
n0r[m] has joined #river
<leon-p>
yes, you'll need a wayland client for that. but you could write one that dumps the data to stdout so you could use it in a script
<n0r[m]>
Here you're assuming I'm capable of writing things beyond shell scripts.
<n0r[m]>
I'd like to, but I suck at actual programming :D
draak has joined #river
waleee has joined #river
draak has quit [Quit: WeeChat 3.6]
Nulo has quit [Read error: Connection reset by peer]
<xaltsc>
Hey, so River only sends the Focused Output event when the focus has changed. Is there any way to get the currently focused output without having to wait for this event, which may not even be sent when there's only one output ?
maxv has quit [Quit: Client closed]
<xaltsc>
Since focused tags events for the outputs are sent upon creation, I was a bit suprised the focused output event wouldn't be sent as well.
<xaltsc>
The inteface spec says that the focused_output event is "Sent on binding the interface", so I may have a bug though.
<leon-p>
It definitely should be send on binding the interface
<leon-p>
i just checked and it does seem to be send on interface bind, as expected
<ifreund>
there's a annoying race that I don't think we've mitigated in river's implementation of this
<ifreund>
if you don't bind the wl_output global before creating the zriver_seat_status_v1 libwayland-client will drop the events
<ifreund>
we mitigate this kind of thing in wlroots for e.g. wl_surface.enter by adding code to send the event on binding the output global if not already sent
<leon-p>
oh right, I remember hitting a similar bug in lswt with foreign-toplevel
<ifreund>
I actually added a fix for that instance of this race in wlroots a while back
<xaltsc>
Yeah, I don't bind anything manually, I wait for wayland-rs to send stuff, and from what I can see from the enumaration of the wl_registry, wl_output is sent later than wl_seat and zriver_status_manager