0.1.4
Fixes
- The delimited inline comment
{% ... %}is highlighted (#30, markup-carve/carve#1239). The comment rules covered%%lines and%%%fences only, so the payload read as ordinary text and the markers inside it stayed live:{% *not bold* %}rendered a bold run inside a comment. Scoped whole, in paragraphs, table cells and block quotes; a{%inside backticks stays code. - A marker separator is a run of spaces, not one space (#33).
^ Captionand## Headingscope the whole run as the marker, so a writer's column alignment is no longer painted as content.
Improvements
- The fenced block quote (#33, markup-carve/carve#1718). A colon fence whose separator is followed by
>opens a block quote - the third member of the sigil family beside the line block's|and the local hard-break block's backslash - so the opener carries the quote's scope rather than a generic container's. - Eleven constructs the syntax never named (#32, #31). The line block, the local hard-break block, admonitions, footnote definitions, reference and collapsed-reference images and hard breaks had no rule at all, so each took the color of whatever construct claimed it first; four more had rules the coverage probe could not see and are now named for what they are.
Package Control
- Upgrade messages for 0.1.3 and 0.1.4 (#34). 0.1.3 shipped without one, so an upgrade from 0.1.2 to 0.1.4 would have skipped its whole set. Both are in
messages.jsonnow, and that upgrade shows both.
Full Changelog: 0.1.3...0.1.4