Bug description
src/hooks/useKeyboardShortcuts.ts implements 8 distinct shortcuts: Ctrl/Cmd+Shift+E (export), M (mute), R (reset), Escape (cancel), 1-9 (preset switch), ? (toggle shortcuts panel), I (set trim in-point), O (set trim out-point). README.md's table (lines 93-100) lists only Ctrl+Enter/Export, Space, M, Escape — and "Ctrl+Enter" doesn't even match the actual code (which uses Ctrl/Cmd+Shift+E, not Enter).
Steps to reproduce
Compare README.md:93-100 against useKeyboardShortcuts.ts:44-87.
Expected behavior
Table should list all 8 real shortcuts with correct key combinations.
Actual behavior
Half the shortcuts are undocumented, and the one export shortcut listed is described incorrectly (Space for play/pause isn't even in the useKeyboardShortcuts hook either — worth double-checking where that one is actually wired before finalizing the fix).
Distinct from #1423, #1118, and #91, which are about the in-app Keyboard Shortcuts panel/? key being broken — this issue is purely about the README's own markdown table being incomplete/inaccurate, independent of whether the in-app panel works.
Bug description
src/hooks/useKeyboardShortcuts.tsimplements 8 distinct shortcuts: Ctrl/Cmd+Shift+E (export), M (mute), R (reset), Escape (cancel), 1-9 (preset switch), ? (toggle shortcuts panel), I (set trim in-point), O (set trim out-point). README.md's table (lines 93-100) lists only Ctrl+Enter/Export, Space, M, Escape — and "Ctrl+Enter" doesn't even match the actual code (which uses Ctrl/Cmd+Shift+E, not Enter).Steps to reproduce
Compare README.md:93-100 against
useKeyboardShortcuts.ts:44-87.Expected behavior
Table should list all 8 real shortcuts with correct key combinations.
Actual behavior
Half the shortcuts are undocumented, and the one export shortcut listed is described incorrectly (Space for play/pause isn't even in the useKeyboardShortcuts hook either — worth double-checking where that one is actually wired before finalizing the fix).
Distinct from #1423, #1118, and #91, which are about the in-app Keyboard Shortcuts panel/
?key being broken — this issue is purely about the README's own markdown table being incomplete/inaccurate, independent of whether the in-app panel works.