-
Notifications
You must be signed in to change notification settings - Fork 892
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
Add a "single column" mode for rustup toolchain list
and friends
#3519
Comments
@tgross35 Thanks a lot for filing this issue! This is also one of the pain points that I often encounter when using Furthermore, one might argue that a one-line script like the following will suffice: rustup toolchain list | cut -d ' ' -f1 | grep nightly-2023- | xargs rustup uninstall @rbtcollins @djc What do you think? Footnotes
|
the (default) in I wonder if dropping that default, making the list more API-like, adding 'rustup toolchain default' or something similar, would make this nicer. I'm a bit skeptical of rustup doing its own globbing here. |
@rbtcollins Okay, I think it would be better to find a workaround then. IMHO it would be nice if we can leave the output as-is and add a new flag specifically to give simple outputs for non-interactive uses. > rustup toolchain list
stable-aarch64-apple-darwin (default)
nightly-aarch64-apple-darwin
> rustup toolchain list -1
stable-aarch64-apple-darwin
nightly-aarch64-apple-darwin I don't quite like Anyway, this change should probably be mirrored to |
I like |
I'll find some time to implement this |
Now that the output format is being changed in #3225, I think we should wait a bit before implementing this. |
*
) when matching toolchainsrustup toolchain list
and friends
Problem you are trying to solve
I update nightly frequently and always wind up with a lot of toolchains that I am unlikely to use again:
There is no easy way to remove all toolchains matching a pattern
Solution you'd like
Allow
*
as a wildcard for removal and other relevant commands so that this works:Notes
rustup 1.26.0 (5af9b94 2023-04-05)
The text was updated successfully, but these errors were encountered: