Skip to content

Unclosed div

An opened ::: fence with no matching close. The lint reports it at its line, and Pandoc warns about it as it reads your book.

What it looks like

::: {.aside type="note"}
A note whose closing fence is missing.

manuscript/chapter.md:5:1: WARN: div is never closed
  │ 5 | ::: {.aside type="note"}
  │   | ^^^^^^^^^^^^^^^^^^^^^^^^
  Pandoc closes it at manuscript/chapter.md:14:1.
  Close it with a line of :::.
WARN: Div at manuscript/chapter.md line 5 column 1 unclosed at manuscript/chapter.md line 14 column 1, closing implicitly.

What it means

The lint finds the opener with no close and names its file:line:column, with your source quoted under it. Pandoc then detects the same fence as it reads your Markdown and emits its own reader-level warning, which Keystone passes through verbatim; a lenient build shows both.

A lenient build still succeeds: Pandoc closes the div implicitly at end of input, which puts everything after the opener inside the div — rarely what you meant. Under strict mode it fails in the lint, before Pandoc runs.

Add the closing fence where the div should end

Building strict turns this warning into a hard stop, so a clean strict build confirms your fences balance.

::: {.aside type="note"}
A note whose closing fence is now present.
:::