Closed antoniogamiz closed 4 years ago
I have tried some of the solutions described in this question, but it does not work (moreover, I installed raku several days ago so I have rebooted my machine a fair number of times).
I have resolved the problem with:
$env:PATH += ";C:\rakubrew\versions\moar-2020.06\install\bin;C:\rakubrew\versions\moar-2020.06\install\share\perl6\site\bin"
But this is temporal, so it would be really helpful if this is done by rakubrew
.
As you already suspected, rakubrew needs to be installed separately for cmd and Powershell. The reason is: Rakubrew does not manipulate the system wide PATH variable but the one of the currently running cmd / Powershell window. As such any changes to the PATH rakubrew does in a Powershell window have no effect on any CMD windows (or the other way around), or even the system wide PATH.
A possible "solution" to this might be to adapt the installation instructions to instruct the user to set up both hooks Powershell and CMD in a single big command. I'm not sure I like this though as the CMD instructions involve quite some manual work and I don't want to put this extra work on everyone that only wants to use rakubrew in Powershell.
Hum, that makes sense. Then, I think a warning in the installation instructions will be helpful.
The following commands have been executed from
cmd
:rakubrew rakubrew-version
?:env
or inshim
mode? (runrakubrew mode
to find out):rakubrew home
to find out):I installed
rakubrew
forcmd
without any problems following the instructions from https://rakubrew.org/. Today, I tried to useraku
andzef
from PowerShell but I get the following error:Do I have to re-install everything following the instructions for PowerShell? It would be really helpful if the
cmd
installation process updates the PATH for PowerShell too. Maybe this is done automatically by Windows (I suppose all terminals should have the same PATH variable).This is the output of PATH variables in each terminal: