Skip to content
This repository has been archived by the owner on Jul 29, 2018. It is now read-only.

Should we support Powershell in Windows? #297

Open
brgnepal opened this issue Jul 6, 2016 · 5 comments
Open

Should we support Powershell in Windows? #297

brgnepal opened this issue Jul 6, 2016 · 5 comments
Milestone

Comments

@brgnepal
Copy link
Contributor

brgnepal commented Jul 6, 2016

It seems that with Windows 10, powershell will be used more often than command prompt as developers point of view.

Also, found that we can able to set the variable temporary per shell session which is needed in our case.
It case be done as:

$env:TestVariable = "This is a test environment variable."

To set permanently,

[Environment]::SetEnvironmentVariable("TestVariable", "Test value.", "User")

More refer here

We should look for supporting powershell in windows for the plugin.

@hferentschik
Copy link
Contributor

+100

@hferentschik
Copy link
Contributor

We need to be able to detect the right shell type though. Right now we rely on VAGRANT_DETECTED_OS which won't work.

@hferentschik
Copy link
Contributor

Actually this is probably a duplicate of issues #293

@LalatenduMohanty
Copy link
Collaborator

@budhrg @hferentschik Do we know if CMD works fine for VSM in Windows?

@brgnepal
Copy link
Contributor Author

@LalatenduMohanty I had created an issue to track CMD here #392.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants