-
Notifications
You must be signed in to change notification settings - Fork 160
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
Support verbose command option #85
base: master
Are you sure you want to change the base?
Support verbose command option #85
Conversation
This is a good idea, thanks! But the implementation you proposed looks a little ugly to me. I'd be much more comfortable with a logging based solution. Then we can just have the |
Added info for 'verbose' flag and updated the list of supported commands.
Hello @devxpy here are the changes for the logging implementation. I have updated the branch to your latest changes and made the logging implementation on top....though (for a reason that I do not know) github sees as commits of this pull request also commits that took place after the initial submission of the Pull Request. If you want the Pull Request to be cleaner, I could close this PR and open a new one. Waiting for your feedback. |
c5ee7ed
to
c0427a3
Compare
c0427a3
to
8b83a71
Compare
…o/ampy into support-verbose-messages
@devxpy finally did a reset and rebase to get rid of all the irrelevant commits. I hope now it would be easier to review. |
Add support to "-v, --verbose" option to the cli.
This will enable printing of progress messages regarding the files that are being handled at the moment.
Affected operations:
(also some whitespaces have been removed automatically by the linter.)