-
Notifications
You must be signed in to change notification settings - Fork 385
Fix nushell env for Windows #3880
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
In nushell, PATH variable is a list, not a string. After load-env, must set $env.PATH to a list.
In nushell, PATH variable is a list, not a string. After load-env, must set $env.PATH to a list.
pinging @AntoinePrv |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #3880 +/- ##
=======================================
Coverage ? 62.91%
=======================================
Files ? 300
Lines ? 37124
Branches ? 2780
=======================================
Hits ? 23356
Misses ? 13716
Partials ? 52 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
I'm no nu expert but this seems good. One question @cvanelteren, does this break currently initiated nushells? For example, if one user has |
The |
This is a fixed pr initialized by @Wuvist. Unfortunately he is MIA. I fixed the commits on that PR and want to push this to the repo to ensure that new users won't have this issue.
What does this PR do?
My initial implementation works well for unix but does not generalize well for windows-based machines. This PR addresses this while fixing an issue that the path was converted to a string.