Repository navigation
Discoverability: where active keys appear #16
Description
Part of the map Map: integration key contract.
Question
Where are the active keys shown: the footer (today r refresh · q quit), the section header, a focus marker, or a combination? Decide how it fits a narrow pane and what shows when keys outnumber the room.
Activity
shayan-ys commentedon Oct 9, 2026
Resolution
The focused section's heading starts with
▸. The footer shows enabled built-in keys, thentab focus(only with two or more keyed integrations), then the focused integration's bindings. It is cut with an ellipsis when narrow.Decided by the agent at Shayan's request (no grilling round, 2026-10-09). Full detail in the spec:
Wiki/02-Projects/Devdash/2026-10-09 1112 Integration key contract.md(private vault).shayan-ys commentedon Oct 9, 2026
Amended (Shayan, 2026-10-09): each keyed integration shows a dim hint row at the bottom of its section (
j newer · k older · s scope), whether or not it has focus; it does not count againstmax_rows. The focused heading keeps▸. The footer shows only built-in keys plustab focusand does not repeat bindings.shayan-ys commentedon Oct 9, 2026
Amended again (Shayan, 2026-10-09), supersedes the hint row: the footer is a single list of key hints with no clock and no
every Ns. It shows built-in keys, thentab focuswhen two or more integrations are focusable, then the focused integration's bindings appended, like the omp session bar. Each section heading counts down to its next fetch:fetched 12s ago · next fetch 48s, orfetching…while a fetch runs. The focused heading keeps▸.shayan-ys commentedon Oct 9, 2026
Amended again (Shayan, 2026-10-09), supersedes the single footer list: each section lists its own keys on its last row — an integration's bindings under its output,
r refreshunder the last PR section — and the bottom row holds onlyq quit(plustab focuswhen two or more integrations are focusable). Headings still count down;▸still marks focus.