fix: escape leading tilde fences after wrap - #591
Open
BetterAndBetterII wants to merge 1 commit into
Open
BetterAndBetterII wants to merge 1 commit into
BetterAndBetterII wants to merge 1 commit into
Conversation
Wrapping can move ~~~ to column 0, which CommonMark treats as a fenced code opener. Escape a leading run of three or more tildes in paragraph() like the other line-start guards. Fixes hukkin#590
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Wrapping can move a
~~~run to column 0, which CommonMark treats as a fenced code opener.paragraph()already escapes other wrap-exposed block openers (#,>, lists, setext, thematic breaks) but not tilde fences, so the AST check then refuses to write.Escape a leading run of three or more tildes the same way ATX headings and
>are escaped. Two tildes stay unescaped (not a fence).Fixes #590