05:49 <mikec> so what exactly will 1100 bring on the user facing end? my understanding is that its a change from layout generators to more general window manager clients, but does it allow those wms to have additional capabilites or anything right now or is it only an implementation detail type thing for now? i read some of the pr but it kinda goes over my head a bit

05:50 <LarstiQ> mikec: yeah, the wms will have more control over doing things differently than riverwm does now

05:51 <LarstiQ> river just doing the compositing in the future

05:52 <LarstiQ> it's been a while since I read the protocol spec but I'm confident in going out on a limb and claiming that for example if you want to write a wm that includes manual layouting (say splitting a focused window) you can do that with 1100 and it's impossible right now (without changing the river code itself to do that, and hence this approach for more flexibility)

05:54 <mikec> will that be possible when the pr drops though or is it more this allows us to easily add the code to do this later

05:56 <LarstiQ> the PR enables others to write things like that, river is getting out of the game of doing window management itself so it won't bring any specific feature like that itself

05:56 <LarstiQ> that said, several people have been writing wms against 1100 so who knows what's ready to go when the PR is merged

05:59 <mikec> is it planned for the current layout generator system to work with rwm or will it be easy enough to write wms that it wont really be needed

06:01 <LarstiQ> that's up to the wm I think whether they implement the layout generator protocol

06:03 <mikec> seems to me like this will be a very neat feature when it gets merged, looking forward to what people come up with

06:04 <mikec> personally I really like the bspwm style window management, so if I can get that on wayland that would be great

06:19 <LarstiQ> yeah it's exciting stuff. River already works rather well for me but there are still a couple of things I might like to try and change

06:24 <mikec> what sorts of stuff are you looking to try

07:07 <Nickli> reminds me of how people build openbox into their tiling wm

07:19 <LarstiQ> mikec: my workflow still is influenced by long usage of awesomewm. It would be a bit smoother with a maximize toggle that is not fullscreen, and a miniimize that leaves the window on the tag but doesn't show it and skips it in focus-view

14:38 <Guest8> Hello all :D

14:38 <Guest8> I'm trying to find out if there is a cmd to list all windows with their app-id and title. Does that exist ?

14:43 <ifreund> Guest8: you can use lswt for that

14:43 <ifreund> https://git.sr.ht/~leon_plickat/lswt, should be packaged for most distros

15:13 <Guest8> Thank you :D

15:13 <Guest8> I think it would be helpful if lswt was mentioned in the man pages of riverctl, specifically where app-id and title are mentioned.

15:44 <Nickli> it is mentioned in the wiki https://codeberg.org/river/wiki/src/branch/master/pages/Recommended-Software.md

16:26 <Guest8> True, but I didn't look there for the information. I was expecting at least a mention that riverctl does not provide a cmd that shows app-id and title.

16:27 <Guest8> a mention in the man pages *