This repository has been archived by the owner on May 5, 2021. It is now read-only.
Remove './' from beginning of file paths, it's unnecessary and breaks th... #4
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
… the file name creation logic
|
Thanks for the quick fix. The dot also has to be escaped or |
jgonera
added a commit
that referenced
this pull request
Mar 15, 2013
Remove './' from beginning of file paths, it's unnecessary and breaks th...
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
...e file name creation logic
This should close #3 -- turns out the problem was caused if you try to pass './' in the srcDir or dstDir arguments. You could just tell people not to do that, but if you just run those vars through a quick
.remove()to remove opening './' from either argument, the problem seems to be solved no matter what.