diff options
| author | user <user@clank> | 2026-08-15 11:45:56 +0200 |
|---|---|---|
| committer | user <user@clank> | 2026-08-15 11:45:56 +0200 |
| commit | e9dddc549de1ecd068fa152bf735a72d3a3d03c9 (patch) | |
| tree | d2c9cef53917a0c444bcd05e03343e31487b9fcb /src/config.h | |
| parent | sl0ppty: the prefix badge names the key you actually bound (diff) | |
| download | slosh-e9dddc549de1ecd068fa152bf735a72d3a3d03c9.tar.gz slosh-e9dddc549de1ecd068fa152bf735a72d3a3d03c9.tar.xz slosh-e9dddc549de1ecd068fa152bf735a72d3a3d03c9.zip | |
sl0ppty: bindings that need no leader
Every binding needed the prefix first, which is the safe design and the
reason a leader exists: a multiplexer that takes chords away from the
programs inside it is a multiplexer you fight. But it is the user's keyboard.
Somebody who wants ctrl+alt+arrow to move between panes should be allowed to
have it, including the part where that chord stops reaching vim.
keys {
direct {
bind "ctrl+alt+left" "focus-left"
bind "ctrl+alt+right" "focus-right"
}
}
A block rather than a flag on each line, because these take a chord away from
every program in every pane, and that is worth seeing at a glance -- and
worth having somewhere to write the warning down, which the config now does
in full: prefer chords no program wants, a bare letter certainly is not one,
`none` gives it back.
Three ordering decisions hold it together, none of them obvious from reading
the code, all three tested:
- the direct lookup happens *last* in the key path -- after the rename editor,
the finder, the cheatsheet, and the prefix itself. An overlay still owns the
keyboard, and a direct binding cannot shadow the leader, which would make
the leader unusable with no way back. There is a test that tries exactly
that and finds the prefix still working.
- `direct` is part of a binding's identity rather than a property of it. `x`
after the leader and `x` on its own are two bindings; binding one must not
silently redefine the other.
- the after-the-leader lookup falls through to direct bindings, so pressing
the prefix first never makes a binding stop working. A rule you have to
keep track of is a rule that will catch you out.
The cheatsheet lists them under "without the leader", apart from the rest,
because the caption at the top of it says "<prefix> then:" and these are
precisely the ones that is not true of.
The tests state the bargain rather than just the mechanism: the chord fires
with no leader, and what it fires on, the program never sees -- asserted with
`cat -v`, so a keystroke arriving in the pane is visible on screen rather
than an invisible control byte that would prove nothing either way.
Diffstat (limited to 'src/config.h')
| -rw-r--r-- | src/config.h | 13 |
1 files changed, 13 insertions, 0 deletions
diff --git a/src/config.h b/src/config.h index 889c16b..c093f93 100644 --- a/src/config.h +++ b/src/config.h @@ -72,6 +72,11 @@ typedef struct { int key; /* GhosttyKey */ uint16_t mods; /* MOD_* */ action_t action; + /* Fires without the leader, taking that chord away from every program in + * every pane. Deliberately possible and deliberately opt-in: it is the + * user's terminal and their keyboard, and a multiplexer that refuses to get + * out of the way is its own kind of wrong. */ + bool direct; } binding_t; typedef enum { ALIGN_LEFT, ALIGN_CENTER, ALIGN_RIGHT } align_t; @@ -270,7 +275,15 @@ bool config_load(config_t *c, const char *path, char *err, size_t errcap); const char *config_default_path(void); void config_free(config_t *c); +/* What a chord does after the leader. Direct bindings answer here too, so + * pressing the leader first never makes a binding stop working. */ action_t config_lookup(const config_t *c, int key, uint16_t mods); +/* What a chord does on its own, with no leader pressed. ACT_NONE for the + * overwhelming majority of keys, which is what lets them reach the pane. */ +action_t config_lookup_direct(const config_t *c, int key, uint16_t mods); +/* Whether any binding fires without the leader, so the cheatsheet knows + * whether it has a section to draw. */ +bool config_has_direct(const config_t *c); /* The reverse of config_parse_chord: what to call a binding on screen. A * shifted letter is written the way you would type it ("H"), because "S-h" is * a description of a keystroke rather than a keystroke. */ |
