-
Notifications
You must be signed in to change notification settings - Fork 41
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
Add output pager to verbose commands #50
Comments
1 task
Looks like Click already has a solution for this (and further down the same page, "Launching Editors") 👏 We should start by trying that out |
LGTM. So to implement that, we need to:
Other (than |
Closed
craigds
added a commit
that referenced
this issue
Jun 2, 2020
Fixes #50. Requires pallets/click#1572.
craigds
added a commit
that referenced
this issue
Jun 5, 2020
Fixes #50. Requires pallets/click#1572.
craigds
added a commit
that referenced
this issue
Jun 5, 2020
Fixes #50. Requires pallets/click#1572.
craigds
added a commit
that referenced
this issue
Jun 5, 2020
Fixes #50. Requires pallets/click#1572.
craigds
added a commit
that referenced
this issue
Jun 9, 2020
Fixes #50. Requires pallets/click#1572.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This came up as part of #48. Some commands generate a lot of output, and mostly we don't pipe them to a pager at the moment.
Some of our commands exec git directly, so those may use a pager already, but over time more of the commands will probably be directly implemented in sno rather than execcing git.
We should add an output pager (presumably usually
less
) and ways of customising it.The text was updated successfully, but these errors were encountered: