-
Notifications
You must be signed in to change notification settings - Fork 23
Conversation
Show 10 events at a time and continue as long as the user wants (as opposed to previously only showing 50 events).
Creating the client will prompt the user for their passphrase when needed. We prefer to do any validation beforehand, so that users don't have to type their passphrase unnecessarily.
While testing I come across the following usability things:
|
I've changed the default to 20 events per page and made it configurable with |
This makes it clearer what is omitted
This uses tty when input is piped
Have you tested this? For me, it just hangs the command without any output. |
Yes, this works on my machine + repo. Note that because the width of columns is determined on the size the data has for each entry in the column, output is only written after the last event has been fetched (on |
…t possible --no-prompt might take way too long, as all events are fetched before any output is shown.
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.
One extra question: what happens in case the output of the command is piped?
They're and should always be positive
This reverts commit a27b9bb.
If tty is available, |
Show 10 events at a time and continue as long as the user wants
(as opposed to previously only showing 50 events).