-
Notifications
You must be signed in to change notification settings - Fork 3.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature Request: Influx CLI #4628
Comments
As a workaround in the meantime you can scan the history file itself at |
@beckettsean Thanks for the note. |
Adding support for the command |
It seems the library used for writing the history file doesn't expose a method to read the history stored in-memory. So the question is whether to fork it and try a PR or implement our own history management. Hints? |
Would it be that difficult to implement our own? It doesn't seem that difficult -- it's just a file with commands in there. We tend to avoid 3rd party libraries if we can help it, so using our own would align better. |
@otoolep on it 👍 |
Unfortunately, |
The influx cli keeps a history of recent commands that were executed which can be accessed using the 'up' arrow key. This is an extremely useful feature on the CLI.
It would be nice to have a CLI specific command that behaves like bash shell's 'history' command.
The output of the command could be a dump of recent commands on the console.
The text was updated successfully, but these errors were encountered: