Set PATH delimiter as per OS to search for Clojure #90
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.
Prior to this change, on Linux or Unix, even if Clojure is available in
one of the paths mentioned in the PATH environment variable, the normal
mode command ,c fails to start Swank server with Clojure. This issue
occurs because semicolon (
;) is assumed to be the path delimiter inthe PATH value, so when PATH is, say,
/usr/bin:/usr/local/binandclojure.jaris available in/usr/local/bin, the search for Clojurefails because Slimv tries to search for Clojure in a single directory
named
/usr/bin:/usr/local/bin. Instead, it should search for Clojurein two directories named
/usr/binand/usr/local/bin.This change ensures that on Linux or Unix, colon (
:) is interpreted asthe path delimiter in the PATH value. On Windows, semicolon (
;) isused as the path delimiter.