<Nosrep>
are there plans to let floating window management be configurable like tiling is in the future or nah
<leon-p>
can you expand what you mean with "configurable"?
<Nosrep>
possible to change how it behaves in regards to stuff like stacking without editing river's source directly
<leon-p>
maybe
<leon-p>
the plan is to move window management completely out of river into the layout generator
<Nosrep>
aight
<leon-p>
however I am not sure yet how well that will work w.r.t. to floating views, as potentially anything involving the mouse requires either a lot of roundtrips with the layout gen (bad option) or a ton of imposable rules for flexibility (slightly better option)
raven_ has quit [Quit: connection reset by purr]
waleee has joined #river
eShaev9z has joined #river
eShaev9z_ has quit [Ping timeout: 260 seconds]
jao has quit [Ping timeout: 245 seconds]
waleee has quit [Ping timeout: 240 seconds]
aryak has quit [Ping timeout: 246 seconds]
aryak_ is now known as aryak
aryak_ has joined #river
trav13642 has quit [Remote host closed the connection]
TheAnachron has joined #river
dagle has quit [Server closed connection]
dagle has joined #river
leopoldek has quit [Ping timeout: 240 seconds]
aryak has quit [Ping timeout: 250 seconds]
aryak_ is now known as aryak
<ifreund>
Nosrep: stacking/rendering order will likely be configurable outside of river. Interactive move/resize with the mouse will likely remain internal to river.
<ifreund>
Nothing is certain though, all of this stuff is just ideas at this stage. I need to actually implement and iterate on it to see if the ideas actually make sense in practice
duncaen has quit [Ping timeout: 258 seconds]
aryak_ has joined #river
duncaen has joined #river
<RZ_MJ[m]>
Maybe river could handle moving/resizing a tiled window itself and when it is done, it tells the layout manager what happened (which window was moved where). Then the layout manager can decide what to do (let the window float or tile it again in a different position with an adjusted layout).
waleee has joined #river
jao has joined #river
raven_ has joined #river
<leon-p>
I think the best option will be to allow the layout gen to attach position / dimensions to cursor movement, while also allowing it constrain the area the cursor can move in. That keeps the annoying logic inside river without sacrificing flexibility or imposing any design decisions on layout generators
<aktina>
leon-p: yesterday you were talking about using nested river sessions to have a terminal multiplexer like workflow, I wish to know how you'd do it
Ordoviz has joined #river
notzmv has quit [Ping timeout: 246 seconds]
waleee has quit [Ping timeout: 245 seconds]
<novakane>
for those interested I finally write a good enough for a beginning software to display tags status in zelbar https://git.sr.ht/~novakane/zelbar-river
fitrh has quit [Quit: fitrh]
JustineSmithies has joined #river
notzmv has joined #river
notzmv has quit [Ping timeout: 246 seconds]
linkert has joined #river
alexherbo2 has joined #river
linkert has quit [Remote host closed the connection]
alexherbo2 has quit [Remote host closed the connection]
linkert has joined #river
alexherbo2 has joined #river
leopoldek has joined #river
linkert has quit [Quit: linkert]
linkert has joined #river
linkert has quit [Client Quit]
<leon-p>
aktina: just run river inside river. you can use the -c flag to point to a different init file that just starts a terminal for example
rick42 has joined #river
<rick42>
Hey everybody! New river user here. Daily driving it now and it's working out great. (coming from bspwm btw.) Many thanks for leon-p for the config article!
<leon-p>
glad it works for you!
notzmv has joined #river
zdykstra has quit [Ping timeout: 260 seconds]
Ordoviz has quit [Quit: WeeChat 4.0.0]
waleee has joined #river
alexherbo2 has quit [Remote host closed the connection]
waleee has quit [Remote host closed the connection]
waleee has joined #river
waleee has quit [Remote host closed the connection]