rami3l

I'll find some time to implement this `--quiet` thing then. Claim.

Now that the output format is being changed in https://github.com/rust-lang/rustup/pull/3225, I think we should wait a bit before implementing this.

Hi! Thanks a lot for filing this issue! I agree that in the long run, it is definitely worthwhile adding integration of non-POSIX shells such as `nu`, `fish` (#478, #2995,...

@oneplusiota Would you like to work on this one?

I think I can try to tackle this after https://github.com/rust-lang/rustup/pull/3225, where the logic of detecting the active/default toolchain is refined.

@rbtcollins Thanks for your clarification! > What I was proposing is that: > > * the channel selection is unaltered from today It is still the case that once the...

> > And writing this has me realise that we also need to provide an escape hatch, for the case where someone has configured defaults that are incompatible with the...

It seems that both the missing components and the missing targets will be installed once an auto-install-invoking command is executed: https://github.com/rust-lang/rustup/blob/f32f91efb5c177eac0d6b17b662d3198aa128826/tests/suite/cli_rustup.rs#L2050-L2061 https://github.com/rust-lang/rustup/blob/f32f91efb5c177eac0d6b17b662d3198aa128826/tests/suite/cli_rustup.rs#L2063-L2068 So I guess the concern about incompatible config...

@rbtcollins is concerned about this change's possibility of making environment isolation in systems like bazel more difficult (cc https://github.com/bazelbuild/rules_rust/issues/2285). Will #2793 become an option in terms of mitigating this issue?...

> Why do you want to keep this out of 1.27.0? It maybe doesn't need to go in, but I don't see any harm from it being merged? > >...