07:19 <vertical24> leon-p: wondering if you have any insights as to why wlopm doesn't work on my intel gpu, but does on the nvidia? absolutely loving river so far, but it's killing my workflow when i know i have to re-arrange all of my views whenever i walk away from my pc for a few minutes

07:26 <leon-p> I am the wrong person to ask here, unfortunately. wlopm itself doesn't actually do anything really. It merely sends a message to the compositor, asking it to turn on/off displaying an output.

07:31 <vertical24> ah ok, good to know (and thanks for the explanation)

07:32 <vertical24> suppose one thing i might try is a hdmi -> display port cable, so that i can use 2x display port with the intel gpu

07:41 <vertical24> oh, and i really like stacktile too. one feature i hope you'll consider is an option to prevent the "primary_count +1" command from incrementing higher than the number of views on the current tag

08:35 <leon-p> Glad you like it. I am not opposed to optionally keeping the amount of views in the primary area capped.

12:25 <leon-p> dnkl: would be kinda cool if fuzzel had the option to treat whitespace separated chunks of input as separate search strings. That would improve the dmenu mode when using inputs consisting of multiple words per line

12:26 <dnkl> leon-p: have you tested latest master? not sure if it's exactly what you're looking for, but it sounds like it

12:27 <leon-p> haven't yet, but will test now

12:34 <leon-p> yep, that's exactly what I want. It also fixes the mild input lag when displaying icons, nice!

12:47 <dnkl> it's really time for a release, but I'd like to finish custom key bindings first

13:18 <ane> hmm, would it be useful to have the name of the layouts and the currently active layout in `riverctl list-inputs` for keyboards?

13:20 <ane> I basically hacked something like this https://paste.sr.ht/~ane/acfc96d7ed7da7595132b5e8552af6ee024f653a

13:21 <ane> basically I want to see the current keyboard layout in my status bar and river doesn't have that info directly yet

13:22 <ane> I hacked that together in like 10 minutes by aping it from sway so the code needs to be refined a liiittle bit :P

13:45 <ifreund> ane: I'd be happy to have that feature, feel free to send that along as a PR and I'll take a proper look when I have time :)

14:19 <ane> ifreund: cool. I'll think about the format a little bit. river assumes wlroots 0.15.1 right? so I can't use wlr_keyboard_from_input_device just yet

14:20 <ifreund> ane: yeah, on 0.15.1 input device still has a union field with a pointer to the keyboard

14:21 <ifreund> for example: https://github.com/riverwm/river/blob/765a3f4aff78945889bbcf05fd01a38f5f80bdf1/river/Keyboard.zig#L80