1.1 KiB
id, title, theme, status, created, date_source, order
| id | title | theme | status | created | date_source | order |
|---|---|---|---|---|---|---|
| shell/ctrl-shows-every-keyboard-shortcut-in-a-modal | Ctrl+? shows every keyboard shortcut in a modal | shell | open | 2026-08-22 | stated | 4 |
Ctrl+? shows every keyboard shortcut in a modal. Stated 2026-08-22, alongside making the bindings configurable. One chord, and the whole set is on screen.
It is the same work seen from the other end, and the order matters: the modal is trivial once a
registry exists and impossible to keep honest before that. Today the bindings live in nine separate
keydown listeners across the app, so a hand-written list of shortcuts would be a second copy of
something nobody updates — a help screen that lies is worse than none. Build it as a render of the
registry from shell/all-keyboard-shortcuts-configurable, never as its own list.
Two things to get right when it is built: the modal should show which bindings apply here versus everywhere, since most of the nine are scoped to one app or panel; and it is the natural place to surface a conflict or a chord the browser refused, because that is when someone is looking.