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
In the powershell installer we load, edit, and save the registry value storing (part of) the user's PATH. In testing in CI I noticed that the value of $env:UserProfile (one of the windows equivs of $HOME) in the current env was appearing in the result. This suggest to me that the values in ci were like %USERPROFILE%/.cargo/bin and in the process of reading/editing we forced those to get substituted permanently, degrading their quality.
We should:
not be substituting existing values
ideally be writing %USERPROFILE% values ourselves when appropriate (as the shell installer does)
The text was updated successfully, but these errors were encountered:
In the powershell installer we load, edit, and save the registry value storing (part of) the user's PATH. In testing in CI I noticed that the value of
$env:UserProfile
(one of the windows equivs of$HOME
) in the current env was appearing in the result. This suggest to me that the values in ci were like%USERPROFILE%/.cargo/bin
and in the process of reading/editing we forced those to get substituted permanently, degrading their quality.We should:
The text was updated successfully, but these errors were encountered: