Unprocessed EditComment Markup
writer
EditComment editorial markup ({>> ...}) was not desugared to a Span during postprocessing.
Q-3-36 — Unprocessed EditComment Markup
EditComment editorial markup
{>> ...}was not desugared to a Span during postprocessing.
What this means
Quarto’s CriticMarkup-inspired comment construct {>> ...} is
parsed as an EditComment AST node — an editorial aside from
one collaborator to another, not intended for the final reader.
Postprocessing rewrites it as a Span with the .comment
class before the writer runs. This error fires when a raw
EditComment 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 an
EditCommentAST node. - A bug in the postprocessor that misses some comments.
How to fix
If a custom filter is in use, ensure it does not produce
EditComment AST nodes after postprocessing. If no filter is
in use, report the document at the Quarto issue tracker.