Fixes: Can't find parser binary on windows when path has spaces #143
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Thank you! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #135 .
The shell interprets spaces as delimiter except when the path is surrounded by double quotes.
Escaping the spaces with Line 34 does not work.
FYI: I also I had to remove the
PHP_PARSER_BINARY_PATHfrom env atlaunch.jsonto be able to work on this on windows since the priority is to the.env.PHP_PARSER_BINARY_PATHnot the generated path.I have not tested this on other platforms so I dont know if it broke something.