Skip to content

Keyboard shortcuts are not not easy to parse visually #368

@nh2

Description

@nh2

In the bottom bar we have the keyboard shortcuts like

[q] Quit [s] Search [←↓↑→,hjkl] Navigation [↵] Open bug [n] New bug [i] Pull [o] Push

Due to the even spacing, when you look into the middle of the bar, their associativity is not easy to read, e.g. is it Open bug [n] or [n] New bug?

Some simple ideas how the UX could be improved:

  • Use alternating text colours (subtle is OK), e.g. [↵] Open bug in white and [n] New bug in grey. Background colours would also do.
  • Use 2 or more spaces, like:
    [q] Quit  [s] Search  [←↓↑→,hjkl] Navigation  [↵] Open bug  [n] New bug  [i] Pull  [o] Push
    
  • Use multiple lines, like:
    Quit  Search  Navigation  Open bug  New bug  Pull  Push
    [q]   [s]     [←↓↑→,hjkl] [↵]       [n]      [i]   [o]
    
  • Use a connecting symbol (possibly also some unicode thing), like:
    [q]_Quit [s]_Search [←↓↑→,hjkl]_Navigation [↵]_Open bug [n]_New bug [i]_Pull [o]_Push
    
    [q]·Quit [s]·Search [←↓↑→,hjkl]·Navigation [↵]·Open bug [n]·New bug [i]·Pull [o]·Push
    
  • Use a separator symbols, like:
    [q] Quit · [s] Search · [←↓↑→,hjkl] Navigation · [↵] Open bug · [n] New bug · [i] Pull · [o] Push
    

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions