List indenting is too picky? #1990
Comments
|
http://johnmacfarlane.net/pandoc/README.html#lists
|
|
This is one of the distinctive ways that Pandoc differs from most implementations. Obligatory link to Babelmark For a rationale behind this behavior, see item number 10 in the motivations behind CommonMark. It's worth noting that the original Markdown specs doesn't explicitly give an example of list-inside-lists but seem to imply a 4-space rule. |
|
+++ Tim T.Y. Lin [Mar 04 15 13:23 ]:
Note also that CommonMark does not use the 4-space rule, and uses a Anyway, bottom line is, if you want your lists to be maximally portable |
|
I see! Thank you all for the help! My 2 cents: It's hard for the user to visually inspect that he has 4*k spaces in a k-level sublist. Thus, if it doesn't make parsing harder, it would be more user-friendly to have this limitation removed. |
|
+++ Alin Tomescu [Mar 05 15 12:28 ]:
If it changes, it will change in the direction of CommonMark. But I think this issue can be closed. |
|
It is not so hard to see if you use a fixed-width font, which you need
|
Closes #3511. Previously pandoc used the four-space rule: continuation paragraphs, sublists, and other block level content had to be indented 4 spaces. Now the indentation required is determined by the first line of the list item: to be included in the list item, blocks must be indented to the level of the first non-space content after the list marker. Exception: if are 5 or more spaces after the list marker, then the content is interpreted as an indented code block, and continuation paragraphs must be indented two spaces beyond the end of the list marker. See the CommonMark spec for more details and examples. Documents that adhere to the four-space rule should, in most cases, be parsed the same way by the new rules. Here are some examples of texts that will be parsed differently: - a - b will be parsed as a list item with a sublist; under the four-space rule, it would be a list with two items. - a code Here we have an indented code block under the list item, even though it is only indented six spaces from the margin, because it is four spaces past the point where a continuation paragraph could begin. With the four-space rule, this would be a regular paragraph rather than a code block. - a code Here the code block will start with two spaces, whereas under the four-space rule, it would start with `code`. With the four-space rule, indented code under a list item always must be indented eight spaces from the margin, while the new rules require only that it be indented four spaces from the beginning of the first non-space text after the list marker (here, `a`). This change was motivated by a slew of bug reports from people who expected lists to work differently (#3125, #2367, #2575, #2210, #1990, #1137, #744, #172, #137, #128) and by the growing prevalance of CommonMark (now used by GitHub, for example). Users who want to use the old rules can select the `four_space_rule` extension. * Added `four_space_rule` extension. * Added `Ext_four_space_rule` to `Extensions`. * `Parsing` now exports `gobbleAtMostSpaces`, and the type of `gobbleSpaces` has been changed so that a `ReaderOptions` parameter is not needed.
Hi, I switched from Markdown to Pandoc 1.13.2 and my lists are not being indented properly anymore.
With Pandoc, this happens:
With Markdown , I would get this, as expected:
If I add another space after the
+sign, Pandoc will indent correctly, but that shouldn't be necessary it seems. I'm assuming backwards compatibility is desired.Any chance you can fix this?
The text was updated successfully, but these errors were encountered: