Summary
Bubble Tea v2 supports the Kitty keyboard protocol, enabling key release detection, key disambiguation, and richer modifier tracking. This could simplify chisel's key dispatch and open up new binding possibilities.
What it enables
- Key release events — distinguish press from release. Could enable hold-to-repeat scrolling in reading mode, or press-and-hold for continuous navigation.
- Key disambiguation —
Shift+Enter vs Enter, Ctrl+I vs Tab, etc. Currently many key combos are ambiguous.
- Rich modifiers —
Ctrl+Alt+Super+Enter is now a single matchable keystroke.
- Auto-repeat detection —
key.IsRepeat flags whether the terminal is auto-repeating a held key.
- PC-101 layout mapping —
key.BaseCode gives the physical key regardless of layout. Useful for game-like bindings.
Current state
chisel has a complex key dispatch tree in model.go — the root model dispatches keys based on view mode (binder, editor, structural views, overlays). Mode-aware routing means keys mean different things in different contexts. The current KeyMsg API works but lacks the richness v2 provides.
Scope
Not a rewrite of the key system — this is about enabling richer input where chisel wants it. The Kitty protocol is progressive: terminals that don't support it fall back gracefully. Enable it, then use the new capabilities where they make sense:
- Reading mode: hold-to-repeat scrolling
- Editor: potential new shortcuts without ambiguity
- General: more reliable modifier detection
Depends on
Summary
Bubble Tea v2 supports the Kitty keyboard protocol, enabling key release detection, key disambiguation, and richer modifier tracking. This could simplify chisel's key dispatch and open up new binding possibilities.
What it enables
Shift+EntervsEnter,Ctrl+IvsTab, etc. Currently many key combos are ambiguous.Ctrl+Alt+Super+Enteris now a single matchable keystroke.key.IsRepeatflags whether the terminal is auto-repeating a held key.key.BaseCodegives the physical key regardless of layout. Useful for game-like bindings.Current state
chisel has a complex key dispatch tree in
model.go— the root model dispatches keys based on view mode (binder, editor, structural views, overlays). Mode-aware routing means keys mean different things in different contexts. The currentKeyMsgAPI works but lacks the richness v2 provides.Scope
Not a rewrite of the key system — this is about enabling richer input where chisel wants it. The Kitty protocol is progressive: terminals that don't support it fall back gracefully. Enable it, then use the new capabilities where they make sense:
Depends on