Ordered list specification

Is an ordered list specified with a sequence of 1. or 1) officially supported / called out in the specification?

At the commonmark.js dingus, an ordered list entered in as follows

1. Foo
1. Foo
1. Foo

appears as

  1. Foo
  2. Foo
  3. Foo

in the output.

The start number of an ordered list is determined by the list number of its initial list item. The numbers of subsequent list items are disregarded.

This is one of those design decisions that has good arguments in either direction.


Thanks for calling out the section. I like using a series of 1s, so if I need to add/remove an option from the list, I don’t have to renumber the list and the list itself is sensical in markdown.

1 Like