Documentation
¶
Overview ¶
Standalone key-capture helper for ini-4pk Phase 0 empirical verification.
Run: go run ./scripts/keycapture/ Press: Enter, Shift+Enter, Ctrl+Enter, Alt+Enter, Shift+Arrow, Ctrl+Arrow, etc. Quit: Esc, or Ctrl+Q.
Writes one line per event to stdout AND to a file at .tmp/keycapture-<pid>.log so the run can be inspected afterwards without copy/paste.
What it reveals: what tcell.EventKey actually produces in your terminal for each key combo, with the outer terminal in its default mode (no kitty/modifyOtherKeys negotiation by initech). The headline question is whether Shift+Enter arrives with Modifiers&ModShift set, or as a plain Enter event (mod=0). The answer determines whether ini-4pk Phase 1 needs to negotiate keyboard enhancement at all.
The tool uses tcell directly, so the parsing is identical to what initech's TUI does. Running this in the same terminal type as your usual initech session gives a representative answer.
Source Files