Nested lists don't quite work properly

Dave's Avatar


22 Aug, 2021 09:57 PM

The product as a whole is fantastic, but I do have one small problem with nested bullet lists. Specifically, create a bullet list such as

  • Item 1
  • Item 2
    • Item 2.1
    • Item 2.2
  • Item 3

Marked doesn't display 2.1 or 2.2 as sub-lists. Putting more whitespace in front of them makes it work, but that causes VSCode's MarkdownLint to complain about too much indentation.

Note that Github's markdown parser does correctly display the sublist list without needing the excess leading whitespace.

// Configuration (do not edit) Marked 2 1022 (Setapp)

macOS Version: 11.5.2

allowPageBreakInCode: YES
bookTxtIsLeanpub: NO
summaryMdIsGitBook: NO
codeIsPoetry: NO
codeCanWrap: YES
collapsibleHeadlines: YES
convertGithubCheckboxes: YES
convertGithubEmoji: YES
convertYAMLToMMD: NO
defaultMathJaxConfig: TeX-AMS-MML_HTMLorMML
defaultPreviewStyle: GitHub
defaultProcessor: MultiMarkdown
enableMiniMap: NO
excludeBlockQuotesFromCounts: NO
excludeFootnotesFromCounts: NO
excludeVerbatimFromCounts: NO
excludeCaptionsFromCounts: NO
folderPreviewExtensionsArray: md, markdown, txt, mdown, html, opml
githubNewlines: YES
h1IsPageBreak: NO
h2IsPageBreak: NO
hrIsPageBreak: NO
includeMathJax: YES
includeKatex: NO
limitTextWidth: NO
mathNumberEquations: NO
mathNumberEquationsSide: 0
mathNumberEquationsAMSOnly: NO
minimalJavaScript: NO
permissionGranted: NO
printHeaderFirstPage: NO
printFooterFirstPage: NO
processHTMLFiles: YES
removeMetadataForPreview: NO
removeYAMLHeaders: NO
scrollToEdit: NO
shouldDetectCritic: YES
shouldHighlightMarkupErrors: YES
shouldLoadCritic: NO
syntaxHighlight: YES
syntaxHighlightOnlyLang: NO
useCustomMarkdownProcessor: NO
useCustomPreprocessor: NO
useFirstH1AsPrintTitle: YES

  1. Support Staff 1 Posted by Brett on 22 Aug, 2021 10:36 PM

    Brett's Avatar

    You're using the MultiMarkdown processor, which requires 4 spaces or a
    tab to indent a list. If you want to use 2 spaces (which isn't valid in
    strict Markdown), switch to the Discount (GFM) processor in

    Aside: MarkdownLint is technically wrong in this case. While many modern
    Markdown processors do accept 2-space indentation, 4 is the strict
    version and no processor I know of will break on it. So if you always
    use 4 spaces, it will work everywhere, if you only use 2, it will break
    in about 25% of Markdown processors. Maybe there's a lint configuration
    you can change this?


Reply to this discussion

Internal reply

Formatting help / Preview (switch to plain text) No formatting (switch to Markdown)

Attaching KB article:


Attached Files

You can attach files up to 10MB

If you don't have an account yet, we need to confirm you're human and not a machine trying to post spam.

Keyboard shortcuts


? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac