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
Is your feature request related to a problem? Please describe.
If #2799 is merged, there may be times when a large history (up to 20 or more) gets built up for a user. Users may want to see this history so that they can switch between specific commands.
Describe the solution you'd like
When you type :history (or an appropriate shortcut), a page is shown that lists the commands you've used sorted by most recent to least recent. Scrolling to one and hitting enter should jump you to that command in your history, and after hitting the last command button (-) you should be returned to the command you were on before you ran the history command
Describe alternatives you've considered
Seeing a visual history adds usefulness but it is not strictly required. Muscle memory and most users likely only caring about the few most recent commands may mean a visual history is not needed. With that said, some users will surely prefer to see a command history for organizational and visual assistance reasons to aid in navigating the command history.
Additional context
Spawned from #2799, I plan on working on this but am open to tweaks. If that PR is not merged, this issue would require similar groundwork.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
If #2799 is merged, there may be times when a large history (up to 20 or more) gets built up for a user. Users may want to see this history so that they can switch between specific commands.
Describe the solution you'd like
When you type
:history
(or an appropriate shortcut), a page is shown that lists the commands you've used sorted by most recent to least recent. Scrolling to one and hitting enter should jump you to that command in your history, and after hitting the last command button (-
) you should be returned to the command you were on before you ran the history commandDescribe alternatives you've considered
Seeing a visual history adds usefulness but it is not strictly required. Muscle memory and most users likely only caring about the few most recent commands may mean a visual history is not needed. With that said, some users will surely prefer to see a command history for organizational and visual assistance reasons to aid in navigating the command history.
Additional context
Spawned from #2799, I plan on working on this but am open to tweaks. If that PR is not merged, this issue would require similar groundwork.
The text was updated successfully, but these errors were encountered: