Description:
The TUI footer displays keyboard shortcuts as l/d/i/o tab which is ambiguous about the key press order. Users may interpret this as pressing the letter first then tab, but the actual working behavior is the opposite.
Current behavior:
- Footer shows:
l/d/i/o tab
- Working behavior: Press
tab first, then l/d/i/o
- Pressing letter first then tab does not work
Desired behavior:
The footer hint should clearly indicate the correct key press order. Options:
- Show as
tab + l/d/i/o to make the order explicit
- Show as
tab: followed by l next, d detail, i input, o options
- Reorder to
tab l/d/i/o (tab first, letters after)
Why this is confusing:
- The current hint
l/d/i/o tab suggests letters come first
- Users naturally try pressing the letter then tab, which doesn't work
- The working pattern (tab prefix) is not discoverable from the hint
- Inconsistent with common TUI patterns that show modifier keys first (e.g.,
ctrl+c, alt+tab)
Impact: Low - usability issue, doesn't break functionality but causes user confusion
Suggested fix: Update the status bar hint to show tab + l/d/i/o or provide clearer documentation of the tab-prefix pattern
Description:
The TUI footer displays keyboard shortcuts as
l/d/i/o tabwhich is ambiguous about the key press order. Users may interpret this as pressing the letter first then tab, but the actual working behavior is the opposite.Current behavior:
l/d/i/o tabtabfirst, thenl/d/i/oDesired behavior:
The footer hint should clearly indicate the correct key press order. Options:
tab + l/d/i/oto make the order explicittab:followed byl next, d detail, i input, o optionstab l/d/i/o(tab first, letters after)Why this is confusing:
l/d/i/o tabsuggests letters come firstctrl+c,alt+tab)Impact: Low - usability issue, doesn't break functionality but causes user confusion
Suggested fix: Update the status bar hint to show
tab + l/d/i/oor provide clearer documentation of the tab-prefix pattern