char_superscript incorrectly handles backslashes #58
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.
Currently, on a superscript grouping ^(like this), backslashes cause an instant end to the group, as though the first backslash seen was a closing paren. This behavior seems undesirable, and most likely unintended.
Example:
^((\^test\))
should result in<p><sup>(^test)</sup></p>\n
, but actually results in<p><sup>(\</sup>test))</p>