Skip to content

Unclosed div

An opened ::: fence with no matching close. This is the one structural mistake that comes with a line number — and it's Pandoc's, not Keystone's.

What it looks like

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

[WARNING] Div at manuscript/chapter.md line 5 column 1 unclosed at manuscript/chapter.md line 14 column 1, closing implicitly.

What it means

Pandoc detects the unbalanced fence as it reads your Markdown and emits its own reader-level warning, which Keystone passes through verbatim — it does no parsing of its own here. Because the message comes from Pandoc's reader, it's the one place you get a real file:line (see Finding the offender for why everything else quotes the element instead).

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.

How to fix

Add the closing fence where the div should end:

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

Every ::: opener needs its ::: closer. Building strict turns this warning into a hard stop, so a clean strict build confirms your fences balance.