-
Notifications
You must be signed in to change notification settings - Fork 17
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
Confusing log output #689
Comments
I think that line is printed before we know if there are errors (which I think we basically pipe through from core PreTeXt). So I'm in favor of this but am not sure how trivial the change is. |
Hmm. It sounds like pretext core should switch to using streams to send messages. That way they can be captured by the CLI and pretty-printed/filtered |
Perhaps core could report "None" when there are none. But this is definitely an issue that belongs with core, not the CLI. |
@oscarlevin is right that this is not CLI territory, but rather for PreTeXt. I have
See PreTeXtBook/pretext@512775a I'm not sure just where/how to best report a |
Forgot to say: thanks @siefkenj for the report, much better now. |
On the command line, the CLI outputs
even if there are no errors. At first glance, I see the word
error
and I think something has gone wrong. I don't think this text is helpful. A blank line would serve just as well to separate it from the previous diagnostic information.The text was updated successfully, but these errors were encountered: