Comments (4)
The original plan was for the format to be utilname: error: msg
in most cases, but I've started to think the error:
bit wastes too much space (as with most of these utilities almost any message written to stderr
is an error).
I'm not entirely sure what you mean by "nested together" unless you are referring to Invalid value for '--bytes <NUMBER>': '-' is not a number or is too large
, which I believe is a result of clap
. I also think the GNU and BusyBox errors messages are not clear unless you already understand how the utility works.
from mesabox.
For the first question:
utilname: error: msg
error: msg
utilname: msg
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:
utilname: error: msg: sub-msg
It looks a little wired (probably because of the prefix utilname: error
). Yes, the current message of GNU and BusyBox is not clear, and I was not suggesting to be consistent with them.
cargo
uses the same format:
$ cargo build -j abc
error: Invalid value: could not parse `abc` as a number
from mesabox.
I think we need to keep everything as one line, so the best way to fix this I guess would be to remove the error:
part.
from mesabox.
Ok, agree.
BTW, I'm coming up this issue when writing testcases for errors.
from mesabox.
Related Issues (20)
- init: Is init a POSIX utility? HOT 2
- Possibility to replace self-maintained test utility with `assert_cli` HOT 7
- Issues with using the utils as shell built-ins
- sleep: not consistent with the POSIX standard HOT 3
- Do we have a guideline for handling error? HOT 8
- sh: escape sequences in bare words parsed incorrectly HOT 1
- Differences between shells
- Drop actual_path? HOT 5
- sh: switch to LALRPOP? HOT 4
- `cargo fmt` does very little HOT 3
- posix/sh: pipeline_subshell test fails in interactive shell HOT 1
- Remove build targets HOT 3
- posix/sh: parser accepts invalid input HOT 1
- Add a wrapper for splice() HOT 2
- The first two tests are blocking for over 60 seconds in Travis HOT 4
- Write testcases HOT 3
- Test coverage is not accurate HOT 6
- NonZero types
- Bindings for calling from C
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from mesabox.