You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While triple codes can be used to introduce a fenced code block, they may also be used to mark an inline code span. However for the sake of list item formatting, this distinction is broken:
* First item
```Triple quoted code```
* Second list item
```More such code```
* Last list item
This ends the list after the first item, starting a new list for the second item. The bullet of the third item gets consumed into the body of the second list item. Taken together I get
<li><p>First item</p>
<p><code>Triple quoted code</code></p></li>
</ul>
<ul>
<li><p>Second list item</p>
<p><code>More such code</code>
* Last list item</p></li>
</ul>
The text was updated successfully, but these errors were encountered:
This moves the distinction between triple-quoted code spans and actual code
fences from the parse_codefence to the is_codefence function. Where the old
code was checking for at least three occurrences of the fence character,
this one here only checks for one, assuming that no language specification
will ever contain backticks.
This also removes setting of a hoextdown-specific variable from the previous
commit, to make the combination compile on base hoedown. Will need to
re-add that assignment when merging with hoextdown.
Fixeshoedown/hoedown#238.
While triple codes can be used to introduce a fenced code block, they may also be used to mark an inline code span. However for the sake of list item formatting, this distinction is broken:
This ends the list after the first item, starting a new list for the second item. The bullet of the third item gets consumed into the body of the second list item. Taken together I get
The text was updated successfully, but these errors were encountered: