Markdown: conflict between multilevel lists and automatic code block formatting

[spearce]

Originally reported on Google Code with ID 79

See sample page at https://gerrit.googlesource.com/gitiles/+/c44a94af693ed2326b68bd47d6659be1f9f7fa60/TEST.md

Whenever multi-paragraph list text is indented 8 or more spaces, gitiles renders it
as a code block. Since it seems list paragraphs have to be indented 4 spaces beyond
the list item in order to be rendered along with the list item (<li><p></p><p></p>),
this effectively limits multi-paragraph lists to only one level deep.

This is sort of related to Issue 73, which notes that nested lists require 4 spaces
of indent to be recognized, rather than just "indented more than the parent". If nested
lists were recognized with only 2 spaces of indent, that would mitigate this problem
a bit, since a list to go to 4 levels before hitting the automatic "8 space" handling.

Alternatively, if the automatic "8 space" handling was removed (it's arguably redundant
with the triple-backtick notation), or at least treated relative to the immediate parent
node, that would solve this entirely.

Reported by None on 2015-06-19 12:24:04

[spearce]

See sample page at https://gerrit.googlesource.com/gitiles/+/c44a94af693ed2326b68bd47d6659be1f9f7fa60/TEST.md

Whenever multi-paragraph list text is indented 8 or more spaces, gitiles renders it
as a code block. Since it seems list paragraphs have to be indented 4 spaces beyond
the list item in order to be rendered along with the list item (<li><p></p><p></p>),
this effectively limits multi-paragraph lists to only one level deep.

This is sort of related to Issue 73, which notes that nested lists require 4 spaces
of indent to be recognized, rather than just "indented more than the parent". If nested
lists were recognized with only 2 spaces of indent, that would mitigate this problem
a bit, since a list to go to 4 levels before hitting the automatic "8 space" handling.

Alternatively, if the automatic "8 space" handling was removed (it's arguably redundant
with the triple-backtick notation), or at least treated relative to the immediate parent
node, that would solve this entirely.

Reported by None on 2015-06-19 12:24:04