You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Originally posted by hqnna January 9, 2025
Unlike other plugins such as the Go plugin which respects environment variables, the Rust plugin for Mise seems to completely ignore if the CARGO_HOME and RUSTUP_HOME environment variables are set in the shell's environment, the code for this can be seen here.
While the ability to set these paths via the Mise configuration file is nice, having it blatantly ignore the environment seems like a poor choice. A good example of why this would be bad is environment configurations that respect the XDG standard, such as my own.
I'm proposing to by default detect the environment variables RUSTUP_HOME and CARGO_HOME from the shell environment, and if not set in the environment fallback to Mise's own configuration file allowing both to be possible and respect shell environment setups.
The text was updated successfully, but these errors were encountered:
jdx
added a commit
that referenced
this issue
Jan 9, 2025
Discussed in #4022
Originally posted by hqnna January 9, 2025
Unlike other plugins such as the Go plugin which respects environment variables, the Rust plugin for Mise seems to completely ignore if the
CARGO_HOME
andRUSTUP_HOME
environment variables are set in the shell's environment, the code for this can be seen here.While the ability to set these paths via the Mise configuration file is nice, having it blatantly ignore the environment seems like a poor choice. A good example of why this would be bad is environment configurations that respect the XDG standard, such as my own.
I'm proposing to by default detect the environment variables
RUSTUP_HOME
andCARGO_HOME
from the shell environment, and if not set in the environment fallback to Mise's own configuration file allowing both to be possible and respect shell environment setups.The text was updated successfully, but these errors were encountered: