Skip to content

config-cli should be inherited automatically by third-party subcommands #11972

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

Closed
glandium opened this issue Apr 14, 2023 · 3 comments
Closed
Labels
C-feature-request Category: proposal for a feature. Before PR, ping rust-lang/cargo if this is not `Feature accepted`

Comments

@glandium
Copy link
Contributor

Problem

When you run cargo --config foo.toml subcommand or cargo --config foo.bar=baz subcommand, where subcommand is provided by a cargo-subcommand crate, the subcommand doesn't act as if the extra config was set.

Compare to git, where git -c foo.bar=baz subcommand does propagate the extra config to the subcommand.

Proposed Solution

No response

Notes

No response

@glandium glandium added the C-feature-request Category: proposal for a feature. Before PR, ping rust-lang/cargo if this is not `Feature accepted` label Apr 14, 2023
@weihanglo
Copy link
Member

Thanks for the report. This seems to be a duplicate of #11031.

@glandium
Copy link
Contributor Author

Indeed, it is.

@weihanglo
Copy link
Member

Thanks. Close in favour of #11031.

@weihanglo weihanglo closed this as not planned Won't fix, can't repro, duplicate, stale Apr 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-feature-request Category: proposal for a feature. Before PR, ping rust-lang/cargo if this is not `Feature accepted`
Projects
None yet
Development

No branches or pull requests

2 participants