Fix ruby executable path resolution on Windows #15
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.
While it's OK to use forward slashes in the executable path on Windows when invoking the executable directly, it does cause issues in some of the more complex use cases, such as when the executable path is used as part of a command pipeline, e.g.:
Replacing
/
with\
in the executable path solves this problem:Making this change fixes a number of failures running
ruby/spec
on Windows.