09:00 <plumeus> TIL about Chimera Linux

13:40 <dnkl> on latest river, I'm seeing an issue with keyboard events when VT switching

13:40 <dnkl> I'm getting a keyboard leave event

13:41 <dnkl> then when switching back, I'm getting keymap, repeat, and modifiers events, but no enter event

13:41 <dnkl> this triggers a crash in foot in the first key press

13:41 <dnkl> I'm thinking this is related to the wl_keyboard not yet having been bound when river wants to emit the enter event?

13:43 <ifreund> dnkl: hmm, yeah that could be it. I wonder what recent commit changed that behavior

13:44 <ifreund> ah, it was almost certainly 5cce49

14:02 <ifreund> dnkl: pretty sure this is a river bug, I'm taking a look

14:03 <dnkl> ifreund: thanks!

14:28 <ifreund> dnkl: should be fixed now, thanks for the report!

14:28 <dnkl> ifreund: great, thanks!

15:02 <NikhilSingh[m]1> how can i map idle-inhibitor to a keymap (waybar idle-inhibitor)

15:57 <n0r> The FAQ says "If no layout generator is active for the current output, river will fall back to floating window management. River is perfectly usable in this floating mode". I've used it for a while. Just wondering: Is the floating modes purpose just serving as a fallback or is it actually intended to be another option among floating window managers? (No implications between the lines, just genuinly curious about the intention)

16:36 <leon-p> n0r: I intended it mostly as a fallback, I did not want river to be totally unusable without a layout generator running because that would make writing layout generators pretty annoying. River is focused on tilting. However I do think the floating mode works well enough that for some people it may be an alternative.

16:37 <leon-p> *tiling

16:38 <leon-p> Although it is a bit more involved than it technically needs to be. The simplest thing to do when no layout generator is running is simply not letting the user move and resize tiled windows at all.

16:40 <ifreund> Eventually the compositor binary itself will likely know nothing about tiling or floating

16:40 <ifreund> I've really gotten busy with other parts of my life recently unfortunately :/

16:46 <n0r> Thanks for the answers :)

19:32 <Guest1734> I'm having an issue with layout generator except for rivertile. When using master and stack configuration with rivercarro or stacktile i see the gap between the last window in the stack and the screen border changing when i open a new window: for instance, when having two window open on a tag the gap is working as it should, but when opening a new

19:32 <Guest1734> window it becomes bigger, so the last window in the stack is higher than it should. Anyone else experienced this?

19:32 <Guest1734> Sorry for bad english

19:41 <leon-p> IIRC rivertile corrects rounding errors, stacktile does not.

19:42 <leon-p> patches welcome :)

19:50 <novakane> hmm I never use outer gaps in rivercarro, so I never saw that, but yeah it probably rounding issue too

20:12 <Guest1734> Is there a way to solve this without patching the source code of the layout generator? Anyway, thanks for the quick reply and the amazing work done on river!

20:13 <leon-p> Unfortunately there isn't. This is an implementation detail in the layout generators.

20:17 <leon-p> Should probably be a simple patch though. Likely just some integer divisions that need to be replaced by ceil.

20:33 <Guest1734> Where should i start if i wanted to try writing this patch?

20:54 <leon-p> Guest1734: in stacktile, likely the split_off_area() and perhaps sublayout_* functions

21:13 <ifreund> if you want an example of how to fix such rounding errors, see e.g. secondary_height_rem in rivertile

21:14 <ifreund> basically, when you do integer division also store the remainder and add that to the size of one of the windows

21:19 <Pound_Hash> Hi, thanks for the wm!

21:19 <Pound_Hash> I've read the docs, but I don't understand all the terminology

21:20 <Pound_Hash> "output" is equivalent to "screen" or "monitor", right?

21:22 <leon-p> Pound_Hash: depends on the backend, but for most regular use cases yes.

21:22 <Pound_Hash> Thanks

21:23 <Pound_Hash> This thing scrolls so much faster than sway

21:23 <Pound_Hash> Both foot and qutebrowser

21:23 <Pound_Hash> Good work

21:28 <Pound_Hash> Sometimes mappings are defined with a "+" and sometimes not

21:28 <Pound_Hash> How do I know if a "+" is needed?

21:29 <leon-p> + is for combining modifiers

21:29 <Pound_Hash> For example, ```# Super+Shift+H and Super+Shift+L to increment/decrement the main count of rivertile(1) riverctl map normal Super+Shift H send-layout-cmd rivertile "main-count +1"```

21:30 <Pound_Hash> The docs here use a "+" to combine the modifier with the basic key

21:30 <leon-p> that's not right

21:30 <Pound_Hash> Okay

21:30 <leon-p> the mods should be separate from the key

21:30 <Pound_Hash> Thanks