Use '~' prefix instead of '%' for random brushes #362
Merged
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 #337.
It's not necessarily the best fix but according to https://en.wikipedia.org/wiki/Filename#Reserved_characters_and_words
~
doesn't seem to be reserved, so it might be a safer bet.It works for me on Linux but I haven't tried other OSes to confirm.
Note that a
~
suffix is used by some code editors to mark backup versions of changed files, which might be a source of confusion (but does show that~
in filenames seems to be safe). It doesn't seem to conflict with~
that expands to$HOME
, at least in bash, as long as you don't use~
alone or with~/somepath
.