starred/markdownlint

Fork 0

mirror of https://github.com/DavidAnson/markdownlint.git synced 2026-04-25 09:16:02 +03:00

[GH-ISSUE #158] Erroneously marks 4 space indentations as warning for unordered lists #124

New issue

Closed

opened 2026-03-03 01:23:56 +03:00 by kerem · 6 comments

kerem commented

2026-03-03 01:23:56 +03:00

Owner

Originally created by @poshcodebear on GitHub (Sep 26, 2018).
Original GitHub issue: https://github.com/DavidAnson/markdownlint/issues/158

When working with unordered lists, if I'm using 4 space indentations (as per the spec), it marks them as invalid with [markdownlint] MD007/ul-indent: Unordered list indentation [Expected: 2; Actual: 4].

Example:

- Base item
    - Indented item

Ordered lists, on the other hand, don't get warnings for either 2 or 4 space indentations.

Since 4 spaces is what's specified in the official spec, and it's more that many implementations let you do 2 spaces, I feel this should be corrected to allow 4 spaces without warnings.

Originally created by @poshcodebear on GitHub (Sep 26, 2018). Original GitHub issue: https://github.com/DavidAnson/markdownlint/issues/158 When working with unordered lists, if I'm using 4 space indentations (as per the spec), it marks them as invalid with ```[markdownlint] MD007/ul-indent: Unordered list indentation [Expected: 2; Actual: 4]```. Example: ```markdown - Base item - Indented item ``` Ordered lists, on the other hand, don't get warnings for either 2 or 4 space indentations. Since 4 spaces is what's specified in the official spec, and it's more that many implementations let you do 2 spaces, I feel this should be corrected to allow 4 spaces without warnings.

kerem

2026-03-03 01:23:56 +03:00

closed this issue
added the
enhancement
label

kerem commented

2026-03-03 01:23:57 +03:00

Author

Owner

@DavidAnson commented on GitHub (Sep 26, 2018):

I don’t think it’s quite true that the spec calls for 4 spaces. For that and more discussion of this topic, please see https://github.com/DavidAnson/markdownlint/issues/141 and linked issues.

_{Sent with GitHawk}

@DavidAnson commented on GitHub (Sep 26, 2018): I don’t think it’s quite true that the spec calls for 4 spaces. For that and more discussion of this topic, please see https://github.com/DavidAnson/markdownlint/issues/141 and linked issues. <sub>Sent with <a href="http://githawk.com">GitHawk</a></sub>

kerem commented

2026-03-03 01:23:57 +03:00

Author

Owner

@poshcodebear commented on GitHub (Sep 26, 2018):

It occurs to me that, when searching to see if this was open, I should have also looked for MD007.

Anyway, thanks for pointing that out! I thought the original design spec said 4, but I'll be the first to point out that I can make mistakes :)

Anyway, if there's any way for it to support both, that would be great; maybe have the rule, instead of "x number of spaces on indent" be something like "consistent indentation size through the document"? I have no idea how doable that is or how much processing that would add to the extension, though.

You mentioned in the other thread that this behavior is configurable; I hunted that down and set MD007 to 4 spaces in my VSCode user settings and that seems to have done the trick for me. Maybe a solution could be adding to the tool-tip somehow to hint that it's configurable, maybe with a link to instructions for that?

Anyway, thank you for this extension, it has helped me get a lot better in my markdown :)

@poshcodebear commented on GitHub (Sep 26, 2018): It occurs to me that, when searching to see if this was open, I should have also looked for MD007. Anyway, thanks for pointing that out! I thought the original design spec said 4, but I'll be the first to point out that I can make mistakes :) Anyway, if there's any way for it to support both, that would be great; maybe have the rule, instead of "x number of spaces on indent" be something like "consistent indentation size through the document"? I have no idea how doable that is or how much processing that would add to the extension, though. You mentioned in the other thread that this behavior is configurable; I hunted that down and set MD007 to 4 spaces in my VSCode user settings and that seems to have done the trick for me. Maybe a solution could be adding to the tool-tip somehow to hint that it's configurable, maybe with a link to instructions for that? Anyway, thank you for this extension, it has helped me get a lot better in my markdown :)

kerem commented

2026-03-03 01:23:57 +03:00

Author

Owner

@DavidAnson commented on GitHub (Sep 26, 2018):

Cool, thanks!

_{Sent with GitHawk}

@DavidAnson commented on GitHub (Sep 26, 2018): Cool, thanks! <sub>Sent with <a href="http://githawk.com">GitHawk</a></sub>

kerem commented

2026-03-03 01:23:57 +03:00

Author

Owner

@DavidAnson commented on GitHub (Mar 19, 2019):

Please see #141 for an explanation of why I don’t see a good way to make everyone happy here.

@DavidAnson commented on GitHub (Mar 19, 2019): Please see #141 for an explanation of why I don’t see a good way to make everyone happy here.

kerem commented

2026-03-03 01:23:57 +03:00

Author

Owner

@poshcodebear commented on GitHub (Mar 19, 2019):

I still think adding a note to the tooltip that this is configurable could help, but either way, thank you for pointing me down that avenue.

@poshcodebear commented on GitHub (Mar 19, 2019): I still think adding a note to the tooltip that this is configurable could help, but either way, thank you for pointing me down that avenue.

kerem commented

2026-03-03 01:23:58 +03:00

Author

Owner

@DavidAnson commented on GitHub (Apr 6, 2019):

Follow-up: I've done this in github.com/DavidAnson/vscode-markdownlint@33ee19a243

@DavidAnson commented on GitHub (Apr 6, 2019): Follow-up: I've done this in https://github.com/DavidAnson/vscode-markdownlint/commit/33ee19a243cba0cee96f01075a92a524504b465a

kerem referenced this issue

2026-03-07 20:03:05 +03:00

[GH-ISSUE #124] Change indent on MD030 - Property indent not allowed. #1952