meta.anchors.content

7 anchors

Specification anchors and declared coverage
Anchor	Implementation	Tests
meta.anchors.content (7)	7 Implemented	7 Implemented
`blocks`	Implemented	Implemented
An anchor’s content starts after its definition marker and includes every subsequent Markdown block until the first applicable closing boundary. Blank lines do not end the content: paragraphs, lists, tables, and code blocks within that extent belong to the same anchor. Read in specification context
`explicit_end`	Implemented	Implemented
A standalone line containing exactly `<!-- end anchor -->`, apart from surrounding horizontal whitespace, ends the active anchor immediately before that line. The comment is excluded from the anchor’s content. Subsequent prose remains outside an anchor until a new definition begins; the explicit marker is optional when another closing boundary already ends the content. Read in specification context
`heading`	Implemented	Implemented
A Markdown section heading ends the active anchor’s content immediately before the heading, regardless of heading level. Both hash-prefixed and underline-style headings are boundaries. Prose following the heading remains outside an anchor until another definition begins. Read in specification context
`literal_syntax`	Implemented	Implemented
Boundary-looking text inside fenced or indented code blocks, inline code, or escaped text does not open or close an anchor. Raw HTML examples do not supply anchor definitions, section headings, or end markers. A standalone end comment acts as a boundary only outside these literal contexts and enclosing HTML blocks. Read in specification context
`next_anchor`	Implemented	Implemented
A new anchor definition ends the preceding anchor’s content immediately before the new marker. The new definition belongs to its own anchor; content extents do not overlap. Read in specification context
`source_end`	Implemented	Implemented
An anchor’s content ends at the end of its containing Markdown document or `.sage` triple-quoted prose block. A `.sage` anchor never captures surrounding language syntax or content from another prose block, declaration, or method. Read in specification context
`unmatched_end`	Implemented	Implemented
An explicit end marker with no active anchor is a validation error. Another end marker after an explicit or implicit end, without an intervening definition, is therefore also an error. An anchor ending at another definition, a heading, or its source boundary does not require an explicit end marker. Read in specification context