It would be useful for reedline to support an optional status bar that is rendered below the current prompt/input area.
For example, an interactive client like scopeql may want to keep the current connection and output mode visible while the user edits a query. Putting this into the prompt makes the prompt noisy, and printing it as normal output means it is no longer tied to the current input.
A status bar below the input area would provide a dedicated place for this kind of context while keeping Prompt focused on prompt text.
Example:
scopeql>
default · http://127.0.0.1:6543 · json · timer on
A possible API shape would be a StatusBar trait whose render() method receives the current editor context and returns the lines to draw.
It would be useful for reedline to support an optional status bar that is rendered below the current prompt/input area.
For example, an interactive client like
scopeqlmay want to keep the current connection and output mode visible while the user edits a query. Putting this into the prompt makes the prompt noisy, and printing it as normal output means it is no longer tied to the current input.A status bar below the input area would provide a dedicated place for this kind of context while keeping
Promptfocused on prompt text.Example:
A possible API shape would be a
StatusBartrait whoserender()method receives the current editor context and returns the lines to draw.