Expand description
Keybinding model — typed key chords + actions.
Operators author bindings declaratively in the shikumi config
(~/.config/tear/tear.yaml). The same vocabulary applies to mado:
when mado embeds tear-core at tier 3, the multiplexer’s bindings
and mado’s bindings come from a unified table so muscle memory
transfers between the two apps.
Structs§
- KeyBind
- Single binding row in a
KeyTable. - KeyChord
- A single key chord — modifiers + key. The string is the
canonical lowercase form:
"ctrl+a","alt+left","super+l","f10". tmux’sC-a,M-Leftshorthand normalises through here. - KeyTable
- A named set of bindings. Tables are looked up by name at chord- dispatch time; the “root” table is the implicit default.
- KeyTable
Name - A keybinding belongs to a named table — most live in the default
"root"table but tmux operators recognise"prefix"(active afterC-b) and"copy"(modal copy mode). Tear honours the same names so dropped-in tmux configs feel native.
Enums§
- Action
- Action a keybinding fires. Variants intentionally mirror tmux command names so a tmux user’s mental model carries over.
Type Aliases§
- KeyTable
Map - The full keybinding store: every table by name. Lives on
crate::TearTheme/ the shikumi config so a reload swaps the whole map atomically.