You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I ran cargo fmt -- --help and didn't get any output. I expected to get the same output that I do get when I run rustfmt --help, especially because the last line in cargo fmt --help says Arguments after `--` are passed to rustfmt.
The weirdest part is if I run cargo fmt -- --help=config, I do get the same output as I get if I run rustfmt --help=config, the configuration specific help. So cargo is passing through --help when it has an argument? And not passing it through when there isn't? I haven't investigated the cause at all, I'm just guessing based on the symptoms.
Steps
Be on stable Rust with the rustfmt component installed.
Run cargo fmt -- --help.
Observe that there is no output.
Observe the expected output by running rustfmt --help.
Notes
Output of cargo version: cargo 1.35.0 (6f3e9c3 2019-04-04)
Output of rustfmt --version: rustfmt 1.2.0-stable (09940a70 2019-03-27)
OS: macOS Mojave
The text was updated successfully, but these errors were encountered:
Uh oh!
There was an error while loading. Please reload this page.
Problem
I ran
cargo fmt -- --help
and didn't get any output. I expected to get the same output that I do get when I runrustfmt --help
, especially because the last line incargo fmt --help
saysArguments after `--` are passed to rustfmt.
The weirdest part is if I run
cargo fmt -- --help=config
, I do get the same output as I get if I runrustfmt --help=config
, the configuration specific help. So cargo is passing through--help
when it has an argument? And not passing it through when there isn't? I haven't investigated the cause at all, I'm just guessing based on the symptoms.Steps
rustfmt
component installed.cargo fmt -- --help
.rustfmt --help
.Notes
Output of
cargo version
: cargo 1.35.0 (6f3e9c3 2019-04-04)Output of
rustfmt --version
: rustfmt 1.2.0-stable (09940a70 2019-03-27)OS: macOS Mojave
The text was updated successfully, but these errors were encountered: