-
Notifications
You must be signed in to change notification settings - Fork 19
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
Better format for error messages #22
Comments
The original plan was for the format to be I'm not entirely sure what you mean by "nested together" unless you are referring to |
For the first question:
I'm not sure which one is better. Seems that Rust's tradition tends to use the second one and "error" is highlighted in red. For the second question, I mean the error message is in one line and separated in colon. E.g., the current one is:
It looks a little wired (probably because of the prefix
|
I think we need to keep everything as one line, so the best way to fix this I guess would be to remove the |
Ok, agree. BTW, I'm coming up this issue when writing testcases for errors. |
The current error messages are not consistent and nested together. We should have a better error message format.
mesabox head:
mesabox cat:
Some examples for reference:
GNU coreutils:
BSD (OS X):
BusyBox:
Cargo:
The text was updated successfully, but these errors were encountered: