26 lines
1.7 KiB
Markdown
26 lines
1.7 KiB
Markdown
---
|
|
name: omp-keybinding-inspection
|
|
description: "Find what a key chord does in omp: doc table, live bundle defaultKeys inspection, modifier names, remap file"
|
|
---
|
|
|
|
Answer "what does chord X do in omp" with evidence from docs + installed bundle, not memory.
|
|
|
|
## Steps
|
|
|
|
1. Read `omp://keybindings.md` — common action IDs and defaults (`Ctrl+R` history search, `Alt+R`/`F5` retry, `Alt+A` agent hub, ...). Docs are not a complete inventory.
|
|
2. Locate the install: `readlink -f $(which omp)` → usually `~/.bun/install/global/node_modules/@oh-my-pi/pi-coding-agent/dist/cli.js` (bundled).
|
|
3. Extract live default chords from the bundle (authoritative for installed version):
|
|
```bash
|
|
cd <dist dir> && grep -o '"app[^"]*":{defaultKeys:[^}]*' cli.js
|
|
```
|
|
Contextual duplicates exist: same chord can map to different actions in different views (e.g. `ctrl+r` = `app.history.search` in composer, `app.session.rename` in resume picker).
|
|
4. Modifier names: `pi-tui/dist/types/keys.d.ts` → `ModifierName = "ctrl" | "shift" | "alt" | "super"`. "mod"/Super binds as `super+`; only shipped super chords are `super+alt+backspace|delete|d`. Most Linux terminals swallow plain Super chords (needs kitty keyboard protocol / CSI u: kitty, foot forward them).
|
|
5. Remaps live in `~/.omp/agent/keybindings.yml` (NOT config.yml): `action.id: chord` or array; `[]` disables. Profile-aware: default-profile file loads first, active profile overrides per action.
|
|
6. In-session live reference: `/hotkeys`.
|
|
|
|
## Pitfalls
|
|
|
|
- `grep pi-tui/dist/*.js` fails (no top-level js; types only under `dist/types/`).
|
|
- Chord notation is case-insensitive, UI-style (`Ctrl+P`, `Alt+Shift+P`).
|
|
- Old unqualified action names auto-migrate; new configs use namespaced ids (`app.*`, `tui.editor.*`).
|