ChanServ changed the topic of #river to: river - a dynamic tiling Wayland compositor || https://codeberg.org/river/river || channel logs: https://libera.irclog.whitequark.org/river/
waleee has quit [Ping timeout: 255 seconds]
groknull has joined #river
groknull has quit [Ping timeout: 272 seconds]
sentry has joined #river
Snetry has quit [Ping timeout: 264 seconds]
groknull has joined #river
groknull has quit [Remote host closed the connection]
eShaev9z_ has joined #river
eShaev9z has quit [Ping timeout: 256 seconds]
angry_vincent has joined #river
groknull has joined #river
groknull has quit [Remote host closed the connection]
eShaev9z has joined #river
eShaev9z_ has quit [Ping timeout: 268 seconds]
eShaev9z_ has joined #river
eShaev9z has quit [Ping timeout: 252 seconds]
leopoldek has quit [Ping timeout: 264 seconds]
leopoldek has joined #river
leopoldek has quit [Remote host closed the connection]
angry_vincent has quit [Ping timeout: 264 seconds]
<leon-p> i wonder if trying to change window geometry of a fullscreened window should be a protocol error for the WM protocol
<leon-p> and the maximize request maybe should be renamed to "inform_maximized" or something similar, to make it clear that it will not affect geometry
<leon-p> also good that capabilities are per-window, that makes sense +1
<ifreund> leon-p: I think there are quite a few protocol errors that could be added (there are none currently)
<ifreund> I find it easier to think about what should be an error while writing concrete implementations
<leon-p> regarding app-id and title: might be helpful to dcoument that windows may have neither an app-id nor a title, so that the WM must not depend on these requests
<leon-p> *events
<ifreund> certainly wouldn't hurt
<leon-p> the protocol does allow moving and resizing arbitrary windows at the same time with the pointer, right? Obviously that's needed for certain tiled layouts. However I don't think the protocol actually reads that way
<leon-p> also it's not described how pointer_warp interacts with pointer confinement
<ifreund> > Multiple windows may be interactively resized at the same time.
<leon-p> that's in the protocol
<leon-p> my point was about resizing one window and moving another window simultaneously
<leon-p> that would be needed f.e. for reimplementing sways window management
<leon-p> IRC isn't really the best for reviews, probably should have put that somewhere else...
<ifreund> hmm, I don't think there's any technical reason to disallow move and resize of two separate windows at the same time it but I'm not seeing the use-case right now
<ifreund> in a tiled layout it you generally want to resize all the affected windows no?
<leon-p> if you have windows tiled in columns and want to resize the layout with the pointer, you need to change size and position of all windows adjacent to the resized border
<leon-p> let me read the resize mechanism again, I might have missed something obvious
<ifreund> resizing from the appropriate edge of the window should be sufficient
<ifreund> e.g. resize from the right edge of the column 1 and from the left edge of the column 2
<leon-p> ah, yeah, I forgot that you can choose the edge, that solves it cleanly
<ifreund> policy over mechanism :)
<leon-p> as it should be
<ifreund> enough code review over IRC: https://codeberg.org/river/river/pulls/1100
kotto has quit [Quit: WeeChat 4.3.3]
waleee has joined #river
kotto has joined #river
angry_vincent has joined #river
angry_vincent has quit [Read error: Connection reset by peer]
<sewn> is there a channel for the rest of ifreund's projects? simon has something similar where the channel is named after himself
<ifreund> sewn: here is fine, there hasn't been enough noise to make creating something else worthwhile yet
angry_vincent has joined #river
<ifreund> (I do have #ifreund registered in case I want it in the future but it's very empty)
leopoldek has joined #river
Guest57 has joined #river
<Guest57> how come firefox does not have a border like the terminal app have?
<Guest57> it seems to have a shadow casted on the background but I would like to see a red line around the firefox window as well, so I know that it is active
<leon-p> Guest57: server side vs client side decoration
<leon-p> river by default respects the wishes of the client
leopoldek has quit [Remote host closed the connection]
<leon-p> you can create a rule to have firefox use server side deco
<leon-p> search for rule-add in the man page
<Guest57> cool, thank you
waleee has quit [Ping timeout: 264 seconds]
<Guest57> yes, worked like a charm. first time I had any use of rule-add. most things in river have defaults that I like
<ifreund> in this case the default comes from the wayland client (firefox) not from river
Guest57 has quit [Quit: Client closed]
angry_vincent has quit [Ping timeout: 255 seconds]
qyliss_ has quit [Ping timeout: 246 seconds]
haliucinas has quit [Quit: .]
qyliss has joined #river
leopoldek has joined #river
aryak has quit [Ping timeout: 272 seconds]
catman has quit [Read error: Connection reset by peer]
aryak has joined #river
aryak has quit [Ping timeout: 268 seconds]
catman has joined #river
angry_vincent has joined #river
qyliss has quit [Ping timeout: 268 seconds]
qyliss has joined #river
siaal has quit [Quit: ZNC - https://znc.in]
siaal has joined #river
enova has quit [Ping timeout: 246 seconds]
waleee has joined #river
angry_vincent has quit [Ping timeout: 264 seconds]
aryak has joined #river
aryak has quit [Ping timeout: 260 seconds]