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
Saving output history solves one half of the problem. Finding a history item should be as easy as saving. I think this may be accomplished with a search feature just like reverse-search-history in bash, but with some cut of the found output. Then an editor of user's choice may be used to open the selected output. Short outputs may be printed directly to stdout.
The text was updated successfully, but these errors were encountered:
Actually I mean searching in commands. Searching in outputs is a good idea too, but it is more complex to implement, and imho this is not so important feature. We still can search through the output history file, right?
So the idea is to add the reverse search feature just like Ctrl+r in bash, but it should give some preview of the command output. And it should open the command output when the user presses the Enter button.
Saving output history solves one half of the problem. Finding a history item should be as easy as saving. I think this may be accomplished with a search feature just like reverse-search-history in bash, but with some cut of the found output. Then an editor of user's choice may be used to open the selected output. Short outputs may be printed directly to stdout.
The text was updated successfully, but these errors were encountered: