-
-
Notifications
You must be signed in to change notification settings - Fork 13
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
feat: history command #97
Conversation
Those flags are probably the most useful options we have, by moving them deeper and effectively removing from the main readme and CLI docs we will make it much harder for people to understand the functionality and to find them. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- if there's no history, the output should be empty, no errors
- the order appears to be reversed; it needs to be old -> new, and the number must match exactly what I'd get when using
ping from @x
- ^ also means commands that use
previous
etc don't get their own number in history, see the example in my original issue (between 2 and 3 there's one without number)
Let's also remove the default limit and show all items by default. |
Also I think all unix tools use |
history
(History command #89)