Installing rust/cargo/rustup is very confusing. #904
Description
I get that proto is used both for project specific toolchain/runtime/version management, but it's also used for global or user-level tooling, like asdf, nvm, etc. To that end, installing npm/pnpm is mostly a pleasure - the fact that installing node doesn't auto install npm or doesn't announce as much during install is a minor inconvenience. But eventually, I can have global and project-specific node and npm as I see fit, without worrying about PATH and whatnot, assuming I use the shim or shell activation approaches.
But rust is another story altogether. I get that it's a different beast entirely, but I poured through source code, docsite, gh issues and such, to figure out why proto install rust doesn't include rustup and cargo. Or why those two aren't offered as their own plugins. I also don't understand why proto install rust then where cargo after a shell refresh produces nothing.
I can see that rustup is installed somewhere. I see that its proxies, including cargo, are installed somewhere. But not anywhere I'd expect - not the usual PATH dirs, nor in ~/.cargo where rustup would install them.
Why does this happen? Or what am I supposed to expect here?
❯ proto bin rust
/Users/rayatrahman/.rustup/toolchains/1.91.1-aarch64-apple-darwin/bin/cargo
❯ cargo
zsh: command not found: cargo
I find using rustup directly or rustup-init closer to what I would expect.
Apologies if this came off rude or ungrateful. I'm genuinely a lil confused, and am likely missing some point somewhere. Either way, I really like using proto and look forward to moving as many things off of asdf, brew, scoop, etc, onto it!