support escapes in reflink definitions #70
Merged
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
Contributor
Author
|
Hrm. Not quite. |
This now works: [link]: http://example.com "Hello, \"World\"!" Allowing escaping the closing delimiter only would make most sense, but for agreement with Pandoc, I included all.
melisgl
force-pushed
the
reflink-title-escape
branch
from
8c29e31 to
81eee3f
Compare
Contributor
Author
|
Alright. This seems to work now. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 now works:
Allowing escaping the closing delimiter only would make most sense, but for agreement with Pandoc, I included all.