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.

Sign up for GitHub

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

add find_msvs custom command to the nu_msvs module #881

Merged

fdncred merged 1 commit into nushell:main from fdncred:update_nu_msvs_with_find_msvs

Jun 18, 2024

Collaborator

fdncred commented Jun 18, 2024

I changed export-env {} at the beginning to a custom command to avoid having export-env run when loading the module
because:

I couldn't use nu_msvs activate because it depends on env vars being set that were hidden with nu_msvs deactivate
It seems that export-env executed at use, leaves $env.FILE_PWD available in the environment which I think may be
a bug. So, putting it in a custom command avoids that.


add find_msvs custom command

0f95f3f

fdncred merged commit ddbebf1 into nushell:main

1 check passed

fdncred deleted the update_nu_msvs_with_find_msvs branch

June 18, 2024 13:09

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment