Skip to content
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

fix debug output during trace #54

Merged
merged 1 commit into from
Nov 5, 2022
Merged

Conversation

algorythmic
Copy link
Contributor

It's a bit confusing that some output (that which is guarded by args.debug) is only present when running with a single -v but not with -vv. I suspect that wasn't the intention.

It's a bit confusing that some output (that which is guarded by
`args.debug`) is only present when running with a single `-v` but
not with `-vv`. I suspect that wasn't the intention.
@MestreLion
Copy link
Owner

It was intentional for some time, as trace (-vv) was an undocumented flag created just to show the git commands executed, and so the debug (-v) lines for each processed file were disruptive. But you're right, this is confusing and counter-intuitive, so it's better to fix. Thanks for the PR!

@MestreLion MestreLion merged commit 26f61b8 into MestreLion:main Nov 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants