Repository navigation
Subcommand run does not search PATH for command argument #641
Description
Activity
Can you clarify what you mean by 'requiring the full path to successfully run the command'? rustup should know the path to the toolchain directory and always be able to find the command in the toolchain directory.
I don't know why
runwould search~/.cargo/bin. The command is for running binaries out of the toolchain directory.I'm not suggesting that
rustup runshould search~/.cargo/binspecifically. Rather, I think that it should search the list of directories in the environment variablePATHwhen the named executable is not found within the toolchain. Its primary purpose may be running toolchain binaries, but it's also the most straightforward way to run a binary that is built with a non-default toolchain and affected by #350.For example, if one uses
cargo installto build and install rusti, one must runrustup run nightly ~/.cargo/bin/rustiin order to run the binary. Runningrustup run nightly rustigives aNo such file or directoryerror, asrustupis not searchingPATH.It seems sensible to me that, unless it would conflict with some other concept in
rustup, therunsubcommand ought to be thought of as providing the proper execution environment for any executable, not just those that make up the toolchain.
Binaries
cargo install'd are placed in~/.cargo/bin(which is in my shell'sPATH), butrustup run <toolchain> foodoes not searchPATH, instead assuming the named executable to be within the named toolchain'sbindirectory and requiring the full path to successfully run the command. This is a change from the behavior ofmultirust, which did searchPATHfor the named command.