lex-primer

Writing correct Lex documents requires using indentation-based structure and the special :: marker rules that replace standard Markdown conventions. You must enforce Lex-specific precedence, required blank lines, and closing-marker formats for tables and verbatim blocks to ensure proper parsing.

Converting Markdown-like content to .lex format fails when typical Markdown habits conflict with Lex-specific conventions. Inline formatting, indentation walls, and annotation attachment rules differ in Lex, requiring you to translate Markdown syntax into the correct Lex document structure to avoid parsing errors.

Lex tables and annotations require specific formatting rules including correct table row formatting, proper closing-marker formats, and strict annotation attachment rules. You must maintain required blank lines around these structural elements and follow inline delimiter rules to guarantee the .lex file parses correctly.

You need to use the :: marker in a .lex file whenever defining structural elements like sessions, definitions, lists, verbatim blocks, tables, and annotations. The :: marker replaces standard Markdown conventions to enforce Lex-specific precedence and indentation-based structure for correct document parsing.

To validate a .lex draft, check title rules, indentation, and element-specific blank-line rules against Lex syntax guidance. Review the document for correct closing-marker formats, table row formatting, and annotation attachment to diagnose and prevent structural parsing failures.

Lex syntax does not directly support Markdown inline formatting and list structures. It uses distinct inline delimiter rules, indentation walls, and specific structural markers that require translating Markdown habits into Lex-specific conventions to maintain document parsing correctness.