Binding Modes

[ghost]

basically just this.

as niri does not have it's own bar, niri msg get_binding_mode should exist (or similiar).

example of how config would look like:

// "default" is implied to not break configs
binds {
    Mod+D { mode "launch"; }
    ...
}

binds "launch" {
    F { spawn firefox; mode "default"; }
    ...
    Esc { mode "default"; }
}

[YaLTeR]

Do you have a case where this provides a considerable improvement over just binding things to keys? I personally never found myself using these much when I was using sway, and the whole accidentally getting stuck in a mode can get rather annoying.

[ghost]

i'm using a "resize" mode in i3, i couldnt just bind those to (a different mod)+hjkl because i've run out of modifier keys

[FreeFull]

When I was using sway, I had a mode configured to disable all sway keybinds (except for the keybind to exit the mode); It's very useful when working with virtual machines, to prevent the compositor from grabbing keyboard input meant for the VM.

[YaLTeR]

That's better handled by the inhibit portal and wlr inhibit

[brainlessbitch]

i'm using a "resize" mode in i3, i couldnt just bind those to (a different mod)+hjkl because i've run out of modifier keys

i have what i assume is a similar mode, and i as i much prefer the controlled resizing of keybinds, i really need this mode back

[ghost]

i've started implementing it

[ghost]

[ehmzee]

Made a GitHub account to say that I would really appreciate this feature!

It'd be nice to be able to add binds more intuitively without the risk of conflicting key combinations. I primarily edit with vi-style bindings in Doom Emacs, and coming from Hyprland, it was nice being able to implement similar modal bindings throughout the rest of the compositor. I also think this could be an improvement for people who use different keyboard layouts, sizes like 60%, or for implementing binds for other, more niche peripherals (Azeron's products come to mind, for example). Being able to implement a mode for a few context-specific bindings--rather than using more complex solutions like switching the keyboard layout, relying on external programs/scripts (and preventing focus conflicts), or hardware-level configuration that may or may not be available--would be really convenient.

This has been the one feature I've sorely missed since I've recently switched to niri.

[YaLTeR]

Hmm, interesting. Do you have an example of such a setup I could look at?

Also, I use a 40% kb myself, works just fine without binding modes :)

[Pajn]

I'd love this as well and non-modal keybinds is a big gripe for me with PaperWM. Primarily working in nvim and wezterm which both provides modal keybinds they are in my muscle memory, and I often try to do WM keybinds by tapping the modifier and then the key which of course doesn't work and I stare at the screen for a while before realizing why it didn't work.

They are also very nice for being able to bind more things without having to figure our more and more elaborate keyboard combinations. The both already mentioned launch and resize modes are something I'd definitely use.

[YaLTeR]

I often try to do WM keybinds by tapping the modifier and then the key which of course doesn't work and I stare at the screen for a while before realizing why it didn't work.

So you want to bind a modifier by itself to go into a mode? That won't work, at least not right away, because we don't have modifier-only binds yet, and it will likely require release binds which we don't have yet either. That said, you might be able to achieve this with something like kmonad already.

[Pajn]

Ah, that's exactly what I wanted to have. But yeah, kmonad or similar could work to make a modifier tap send a chord.

But still, I'd also appreciate "normal" binds to modes to have a resize mode use hjkl and a launcher mode use simple mnemonics without worrying about collisions.