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

Jump to bottom

Powershell path parsing problem (Windows) #2

Open

raphaelreyna opened this issue Jul 8, 2020 · 1 comment

Labels

bug

Collaborator

raphaelreyna commented Jul 8, 2020

When the -s flag is used to pass in a shell to use, oneshot parses the path as having double slashes. This then leads to a 'file not found' error.

example: C:\Windows\System32\WindowsPowerShell\v1\powershell.exe -> C:\Windows\System32\WindowsPowerShell\v1\powershell.exe

raphaelreyna added the bug label

Collaborator Author

raphaelreyna commented Jul 9, 2020

This was somewhat resolved by making PowerShell the default shell on Windows.

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