Skip to main content

Unprocessed Highlight Markup

writer
Highlight editorial markup ({== ...}) was not desugared to a Span during postprocessing.

Q-3-35 — Unprocessed Highlight Markup

Highlight editorial markup {== ...} was not desugared to a Span during postprocessing.

What this means

Quarto’s CriticMarkup-inspired highlight construct {== ...} is parsed as a Highlight AST node. Postprocessing rewrites it as a Span with the .mark class before the writer runs. This error fires when a raw Highlight node reaches the writer.

This is a defensive guard. The condition is a pipeline bug, not a source-level mistake.

Why this happens

Two known triggers:

  • A Lua filter ran after postprocessing and reintroduced a Highlight AST node.
  • A bug in the postprocessor that misses some highlights.

How to fix

If a custom filter is in use, ensure it does not produce Highlight AST nodes after postprocessing. If no filter is in use, report the document at the Quarto issue tracker.