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

Subcommand wasn't recognized #73

Closed
tinywombat765 opened this issue Mar 24, 2018 · 5 comments
Closed

Subcommand wasn't recognized #73

tinywombat765 opened this issue Mar 24, 2018 · 5 comments

Comments

@tinywombat765
Copy link

When I run cargo install-update -a I get:

error: The subcommand 'install-update' wasn't recognized
        Did you mean 'install'?
If you believe you received this message in error, try re-running with 'cargo -- install-update'
USAGE:
    cargo [OPTIONS] [SUBCOMMAND]
For more information try --help
@nabijaczleweli
Copy link
Owner

nabijaczleweli commented Mar 24, 2018

While I intellectually understand why one'd report the fourth duplicate of #68 I will never really understand the necessity for such axion.

@nabijaczleweli nabijaczleweli changed the title subcommand wasn't recognized Subcommand wasn't recognized Mar 24, 2018
@tinywombat765
Copy link
Author

Well if you left #68 open until the issue was fixed (even if not a bug in cargo-update itself) people would see it and stop opening new issues (at least I wouldn't have).

@nabijaczleweli
Copy link
Owner

Well if people did their due diligence and went through closed issues they'd see the previous four issues on the topic :v oh well

@kbknapp
Copy link

kbknapp commented Mar 24, 2018

This has finally made it into the latest nightly cargo build too - so the fix is rustup update nightly

@nabijaczleweli
Copy link
Owner

Thank @kbknapp, eternal praise be unto him.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants