1) pressing arrow_up 3 times -> normal behaviour
2) pressing it Nth time -> very similar behavior but 10 history entries are shown
pressing enter, arrow_right, arrow_left, etc. should behave the same way as they do on the command line
pressing Ctrl-R opens RESH CLI
pressing Ctrl-G, Ctrl-C, Ctrl-D, etc. closes the view with 10 history entries
Motivation
Many people I have observed press arrow up many times with the hope that "the command has to be there" or "it has to be the next one".
Observing workflows of people also shows that we press arrow up when we want recent history entries even when the command is not that recent.
Showing the next 10 commands will preserve the workflow of recalling recent history entries but will allow us to quickly scan the results and tell if the history entry is there or not.
This could help us:
Quickly recognize that the command is not there (then we can try a different way to recall it)
Navigate to the command faster (because we don't have to read each new command separately)
Additionally, the larger view could include a few carefully selected features.
Description
1) pressing
arrow_up
3 times -> normal behaviour 2) pressing it Nth time -> very similar behavior but 10 history entries are shownenter
,arrow_right
,arrow_left
, etc. should behave the same way as they do on the command lineCtrl-R
opens RESH CLICtrl-G
,Ctrl-C
,Ctrl-D
, etc. closes the view with 10 history entriesMotivation
Many people I have observed press arrow up many times with the hope that "the command has to be there" or "it has to be the next one".
Observing workflows of people also shows that we press arrow up when we want recent history entries even when the command is not that recent.
Showing the next 10 commands will preserve the workflow of recalling recent history entries but will allow us to quickly scan the results and tell if the history entry is there or not. This could help us:
Additionally, the larger view could include a few carefully selected features.