Motivation

To validate the parser we'll try printing the AST back to org-mode source - if that works we can be kind of sure that the parsing worked. At least I hope so - I would like to get around writing tests for the individual parsing functions...

Headlines with TODO status, priority & tags

Headline with todo status & priority

Headline with TODO status

Headline with tags & priority

this one is cheating a little as tags are ALWAYS printed right aligned to a given column number...

Lists

• unordered list item 1

• unordered list item 2 - with inline markup

  1. ordered sublist item 1

     1. ordered sublist item 1
     2. ordered sublist item 2
     3. ordered sublist item 3
  2. ordered sublist item 2

• unordered list item 3 - and a link and some lines of text

  1. and another subitem

     echo with a block

  2. and another one with a table

     a	b	c
     1	2	3

     and text with an empty line in between as well!

• unordered list item 4

Inline

• emphasis and a hard line break
  see?
• .emphasis with dot border chars.
• emphasis with a slash/inside
• emphasis followed by raw text with slash /
• ->/not an emphasis/<-
• links with slashes do not become emphasis: https://somelinkshouldntrenderaccidentalemphasis.com/ emphasis
• underlined bold verbatim code strikethrough
• bold string with an *asterisk inside

• links

  1. regular link https://example.com link without description
  2. regular link example.com link with description
  3. regular link to a file (image)

Footnotes

• normal footnote reference ¹
• further references to the same footnote should not ¹ render duplicates in the footnote list
• inline footnotes are also supported via ².