-
Notifications
You must be signed in to change notification settings - Fork 3
Windows compatibility #14
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
ttencate
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ugh, here I was thinking that bash was weird... turns out cmd is ten times worse :(
Agreed, Powershell exists for a reason |
|
Are you still planning to work on this PR? If you don't have time, I'd be happy to take over and push it across the finish line, but I could still use your help with testing all the weird edge cases. |
|
Squash committed all that's needed for it to work! @ttencate |
…D://) and weird names (e.g. "%%^")
|
It should be a-ok now. |
|
Alright, let's go! Thanks a lot! |
fixes #3
Added the current compatibility status, implemented a working cmd.exe call, checked for invalid working directories and improved three things on subprocess.gd. I am not sure if the change on the deferred call is an improvement but it removes the need to use strings, which makes it safer overall.