00:04 <milesrout> I'm really liking river so far. at first I thought the external program for layout was just a bit of Unix philosophy fetishism but it immediately proved useful when I switched in rivercarro instead of rivertile to get dwm-like monocle mode!

00:05 <milesrout> i always much preferred dwm over i3 so while i very much appreciate the stability of sway, having dwm-style tags in a wayland compositor is great.

00:26 <waleee> milesrout: stacktile provides some of the missing bits of i3 (sublayouts so you can have a monocle-layout on one half of the screen, which emulates the i3 tabs a bit)

00:31 <milesrout> i always found i3/sway far too complicated. i'd press something and suddenly i'd have some weird split within a split within a tab within a split and i didn't know how to get out of it

00:32 <milesrout> no matter how long i used it i just didnt form a mental model of how all those bits fit together

00:32 <milesrout> i've used dwm for maybe 10 years now - easier to stick with what you know

00:54 <plumeus> I think the split can be escaped with Mod e, usually. I found dwm's Mod b,d,i to be hard to remember too because I used it so infrequently.

08:15 <ifreund> milesrout: thats exactly why I started working on river, I could never make peace with i3's complexity and implicit state either

08:15 <ifreund> glad river's been useful to you :)

08:58 <angry_vincent> i also switched from i3/dwm/sway.

10:00 <p00f1> > milesrout: splitception

10:00 <p00f1> omg this so much

10:00 <p00f1> and sometimes it goes away if you kill all the windows and sometimes it doesnt

10:06 <p00f1> can someone tell me how i should go about investigating https://github.com/riverwm/river/issues/581 ?

10:20 <ifreund> p00f1: this is the only place in sway's code that I see it do anything related to the keyboard leds: https://github.com/swaywm/sway/blob/9162b536f69cb69466fb4fcfa24d282fa54b122b/sway/input/keyboard.c#L1049-L1064

10:21 <ifreund> river doesn't have any similar code to update led state. I don't understand exactly what it does or why it is necessary though

10:22 <ifreund> river's keyboard code is also a good deal simpler than sway's currently, the place to insert similar code in river would probably be in Keyboard.init()

10:22 <ifreund> https://github.com/riverwm/river/blob/e1ab51f26071958bbeb2d0c637d3d00eb4326fdf/river/Keyboard.zig#L53-L55

10:32 <ifreund> `xkbcli interactive-wayland` might be useful for debugging

10:46 <p00f1> thanks, i'll try to look into this 🙏

11:13 <ifreund> no problem!

13:02 <bucketman> not able to run river in virtualbox usably, M-S-Return doesnt launch foot, only M-S-E causes to exit, able to run weston and use it.

13:03 <bucketman> From inside a weston session though able to launch and run river usably

13:16 <ifreund> kinda sounds like whatever environment you are running virtualbox is eating the keybindings you intend for river

13:23 <bucketman> The keybound event are coming to river when river is run from within a weston session, i doubt if weston initializes input where river fails to, i however need to test events whether they come to river, is there a way to do that?

13:56 <ifreund> hrm, they left