01:22 <gbrlsnchs> With rwm protocol it's possible to keep track of PIDs for programs spawned by your WM, as long as it handles that.

11:50 <seNex> hi! I read about river in some dubious subreddit, installed it, configured it and its awesome! Thank you for this piece of software. I was never that satisfied with an windowmanger and (i tried a lot of them)

12:20 <TheAnachron> seNex same, are you coming from Wayland or Xorg?

12:20 <seNex> my last wm was sway, but I also used a lot of x windowmanager

12:23 <seNex> TheAnachron the tag system was the missing part i missed all the time. One of my first WMs was awesomewm

12:27 <seNex> is it possible to let windows stay in tiling mode while beeing resized with the mouse, instead of automatically going to floating mode? Its not as important, but it would be a nice convinience, since almost every other wm stays in tiled mode. Where does this design choice come from?

12:27 <seNex> This is from the "docu":

12:27 <seNex> resize horizontal|vertical delta

12:27 <seNex> Resize the focused view along the given axis by delta logical pixels. The view will be set to floating

12:38 <LarstiQ> afaik currently not possible with mouse, though you can with riverctl commands triggered by keybindings

12:39 <LarstiQ> (and for the future that would depend on what rwm using projects will implement)

13:00 <leon-p> seNex: the design choice comes from how layouts work: Within the limitations of layout generators (earlier even than the layout protocol), it is impossible to communicate an interactive resize between layout generator and river itself. As such, I decided that rather than doing nothing, interactively resizing a window just floats it

13:08 <LarstiQ> is that also due to the fact that the layout protocol doesn't really track identity of windows?

13:28 <zuki> I've been trying to make a patch for dwl for fun that allows the use of riverctl for controlling dwl, but have been struggling to get it working I'm over half way there I've got riverctl able to connect to dwl, and get the args sent as well as the run command request but I can't figure out how to properly send the

13:28 <zuki> `zriver_command_callback_v1_send_success` without segfalting

13:28 <zuki> here is the w.i.p patch if anyone wants to help https://pastebin.com/raw/BiCzCscn

13:28 <zuki> i've built it upon the newist git commit of dwl

13:57 <zuki> AHHH i got it nevermind

14:22 <LarstiQ> zuki: what was it?

14:29 <zuki> what was it that I just got or what was the fix?

14:29 <zuki>     struct wl_resource *callback_interface = wl_resource_create(

14:29 <zuki>         client, &zriver_command_callback_v1_interface, zriver_command_callback_v1_interface.version, callback);

14:29 <zuki>     zriver_command_callback_v1_send_success(callback_interface,"output");

14:29 <zuki> adding these lines to zriver_control_run_command fixed it

14:30 <zuki> I was working on a patch for dwl that allows the use of riverctl to add binds and such.

19:13 <gbrlsnchs> some window management development fun: https://media.hachyderm.io/media_attachments/files/114/926/773/457/889/561/original/28bc881684b4268a.png 😀

19:59 <Nickli> what would you call stacking windows like that?

19:59 <Nickli> archive view?

20:08 <TheAnachron> I'd call it "Microsoft Solitaire Endscreen"

20:14 <TheAnachron> (For those who dont know: https://www.youtube.com/watch?v=uev21NTzom8)

20:33 <gbrlsnchs> Nickli: I call it "cascading"