-
Notifications
You must be signed in to change notification settings - Fork 402
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
error/warning count in output #655
Comments
While this is very easy to implement as Therefore I would suggest to include a message counter at the very end like this: Current:
Suggestion:
or in a one-liner:
What would you prefer, @mattgarrish? |
I'd vote to save space and go with the latter. The more actual errors you can read from the command line without scrolling the better. You could maybe save some further space by trimming to:
|
I implemented this in PR #742. However, I had to make changes to the |
I was just doing some work on generating an epub from the specs and got to thinking it would be nice to see the total error/warning count after the message that the file contains errors.
When I'm tweaking xslts, it's not always clear if I've fixed the problem without scrolling back through all the messages output to the console. A count would at least give me a quick visual whether things have gotten better, worse or stayed the same.
Anyway, another of my non-critical feature requests...
The text was updated successfully, but these errors were encountered: