travankor has quit [Remote host closed the connection]
travankor has joined #river
yyp_ has joined #river
yyp has quit [Quit: have a great day]
yyp_ is now known as yyp
exception_ has joined #river
exception_ has quit [Client Quit]
exception_ has joined #river
exception_ has quit [Remote host closed the connection]
exception_ has joined #river
exception_ has quit [Client Quit]
exception_ has joined #river
exception_ has quit [Client Quit]
yyp has quit [Quit: disconnected]
yyp has joined #river
yyp has quit [Read error: Connection reset by peer]
gspe has quit [Quit: gspe]
gspe has joined #river
<ifreund>
aha, we don't have perfect frame perfection when transfering views between outputs on master, it's not just the river-layout branch
<ifreund>
and I know why
<ifreund>
leon-p: pushed a commit to your branch that fixes all the issues I've currently seen through usage (aside from transfering views between outputs as noted above)
<ifreund>
what's left to do now is testing and code cleanup then we can finally merge this
<ifreund>
I'm going to switch over and start daily driving it I think
<ifreund>
hmm, we could probably to set default options for new outputs
<ifreund>
*could probabaly use a way to...
<leon-p>
ifreund: simple: it's time to finally introduce hooks. Basically if we could execute a command whenever a new output appears, the problem is solved.
<ifreund>
which can already be implemented in userland with some daemon that listens for new output globals...
<leon-p>
that works too
<ifreund>
not very user friendly though I must admit
<leon-p>
maybe if e shipped such a daemon with river and have an example in the default init?
<ifreund>
well yeah, riverctl could have a mode where it stays alive and listens for evens
<ifreund>
i3 has something like this with their subscribe command
<leon-p>
or we just have hooks and accept that we have functionality in the server that could technically be done with a client. I am fine either way.
<ifreund>
I'd prefer to not add more server side code if it can be avoided
<ifreund>
need to investigate how nice this can be made client side
<leon-p>
the problem is adressing the ouptput. even if we had `riverctl output-hook <command>`, how would the command actually affect the new output and not the currently focused one?
yyp has joined #river
snakedye has joined #river
<ifreund>
well, xdg-output names are stable
<ifreund>
I don't know about details though, will need to give it some thought