Feature Vision Discussion: History

This issue is part of the larger vision discussion managed in #63 to brainstorm and prioritize ideas around features that would make reedline as a line editor for you both viable as well as pleasant to use. Feel free to up-vote features you depend on in other tools/shells as well as suggest new ideas!

History Features

• Ability to save commands in history
• Ability to save multi-line commands in history
• Ability to traverse backward and forward within history via keybindings
• Ability to search history
• Ability to search history and travese backward and forward within the search criteria
• Ability to have rich data within the history, such as:
  • run time in ms
  • date/time command was ran
  • sessionid of who ran the command assuming multiple sessions
• Ability to have multiple sessions successfull write to history file(s)
• Ability for each session to have it's own history or the appearance of it's own history so within history searching in a single session you only see the commands you created in that session
• Ability to send all commands from all sessions into a global history which search interfaces can use
• Ability to have plugable technologies to make history searching and recall extensible

Start with the larger vision discussion in issue #63 and review the unchecked history goals in this issue: global history across sessions and pluggable search technologies. Define the desired behavior and scope there before identifying implementation entry points or tests; done criteria are not specified in the issue.