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

Incorrectly suggests --verbose when subcommand fails #2673

Closed
kornelski opened this issue May 11, 2016 · 1 comment
Closed

Incorrectly suggests --verbose when subcommand fails #2673

kornelski opened this issue May 11, 2016 · 1 comment

Comments

@kornelski
Copy link
Contributor

kornelski commented May 11, 2016

$ cargo clippy
thread '<main>' panicked at 'need to specify SYSROOT env var during clippy compilation or use multirust', ../src/libcore/option.rs:699
note: Run with `RUST_BACKTRACE=1` for a backtrace.
error: third party subcommand `cargo-clippy` exited unsuccessfully

To learn more, run the command again with --verbose.

I tried again with --verbose and got exactly the same output, asking for verbose again:

$ cargo clippy --verbose
thread '<main>' panicked at 'need to specify SYSROOT env var during clippy compilation or use multirust', ../src/libcore/option.rs:699
note: Run with `RUST_BACKTRACE=1` for a backtrace.
error: third party subcommand `cargo-clippy` exited unsuccessfully

To learn more, run the command again with --verbose.

So I thought maybe it's like git which has a different interpretation of options before a subcommand:

$ cargo --verbose clippy
error: Invalid arguments.

Usage:
    cargo <command> [<args>...]
    cargo [options]

Nope :/ So it seems --verbose doesn't work in that situation, and the recommendation is out of place.

alexcrichton added a commit to alexcrichton/cargo that referenced this issue May 11, 2016
Assume they take care of error printing, so just ferry along the exit status if
they fail

Closes rust-lang#2673
bors added a commit that referenced this issue May 11, 2016
Don't print extra error info for subcommands

Assume they take care of error printing, so just ferry along the exit status if
they fail

Closes #2673
@kornelski
Copy link
Contributor Author

Thank you :)

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

No branches or pull requests

1 participant