Work around silly issue with case-insensitive filesystems. #29
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
shashi
added a commit
that referenced
this pull request
Jun 8, 2015
Work around silly issue with case-insensitive filesystems.
|
Awesome, thanks! :) |
Closed
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.
This is really a Julia issue (JuliaLang/julia#9079, maybe others?), but if you follow the readme on a system with a case-insensitive filesystem (like OSX, by default), escher will hang because
import Markdownwill try to loadexamples/markdown.jl.Obviously this isn't great, because you could still accidentally sabotage escher by naming a file after anything it imports, but a proper solution should be in julia, like looking in the package directory before trying to load from the working directory.