fix compilation error with literal newline (#5) #6
Conversation
This file contains hidden or 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
Open
|
see my comment on issue #5. this is not quite the right fix. (nonetheless, the real mystery is why no fix at all has been added to the master branch in the last 23 months. there seem to be two people with commit access to this repo, but a showstopper bug hasn't been fixed. has active development moved to some other fork?) |
Literal newlines need to be inside backticks not double quotes. Fixes lemnos#5.
aspiers
force-pushed
the
fix-literal-newline
branch
from
62db4c2 to
fedf227
Compare
|
Good catch; updated the PR accordingly. I guess the maintainers probably lost interest and/or don't use this tool any more. |
|
I've also merged into the |
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.
Literal newlines need to be inside backticks not double quotes.
Fixes #5.