You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At the moment, in-app keyboard shortcuts require using the ctrl key. For example, in order to quit the application you have to press ctrl+q. This isn't typical of a TUI, e.g. see how ncdu does things.
The reason we need the composite shortcuts is due to the various input fields within the application. For example: the search box. When searching, if the query term(s) contains a shortcut key, e.g. q, the shortcut will be invoked when that key is pressed in order to add it to the query. Thus, in order to solve this issue, we need to separate recognizing application navigation from field inputs.
The text was updated successfully, but these errors were encountered:
At the moment, in-app keyboard shortcuts require using the ctrl key. For example, in order to quit the application you have to press ctrl+q. This isn't typical of a TUI, e.g. see how
ncdu
does things.The reason we need the composite shortcuts is due to the various input fields within the application. For example: the search box. When searching, if the query term(s) contains a shortcut key, e.g. q, the shortcut will be invoked when that key is pressed in order to add it to the query. Thus, in order to solve this issue, we need to separate recognizing application navigation from field inputs.
The text was updated successfully, but these errors were encountered: