[GH-ISSUE #303] Support EditorConfig for configuration #259

New issue

Closed

opened 2026-03-03 01:25:12 +03:00 by kerem · 4 comments

kerem commented

2026-03-03 01:25:12 +03:00

Owner

Originally created by @ejball on GitHub (Jul 3, 2020).
Original GitHub issue: https://github.com/DavidAnson/markdownlint/issues/303

It would be great if we could configure markdownlint in an .editorconfig file. The syntax could be very similar to the JSON configuration, e.g. the options.config example could look something like this:

[*.md]
markdownlint.default = true
markdownlint.MD003.style = atx_closed
markdownlint.MD007.indent = 4
markdownlint.no_hard_tabs = false
markdownlint.whitespace = false

Originally created by @ejball on GitHub (Jul 3, 2020). Original GitHub issue: https://github.com/DavidAnson/markdownlint/issues/303 It would be great if we could configure markdownlint in an [`.editorconfig`](https://editorconfig.org/) file. The syntax could be very similar to the JSON configuration, e.g. the [options.config example](https://github.com/DavidAnson/markdownlint#optionsconfig) could look something like this: ``` [*.md] markdownlint.default = true markdownlint.MD003.style = atx_closed markdownlint.MD007.indent = 4 markdownlint.no_hard_tabs = false markdownlint.whitespace = false ```

kerem

2026-03-03 01:25:12 +03:00

closed this issue
added the
question
label

kerem commented

2026-03-03 01:25:13 +03:00

Author

Owner

@DavidAnson commented on GitHub (Jul 3, 2020):

Do you mean for the markdownlint CLI and/or VS Code extension? This library already supports alternate parsers for configuration: https://github.com/DavidAnson/markdownlint#parsers

@DavidAnson commented on GitHub (Jul 3, 2020): Do you mean for the `markdownlint` CLI and/or VS Code extension? This library already supports alternate parsers for configuration: https://github.com/DavidAnson/markdownlint#parsers

kerem commented

2026-03-03 01:25:13 +03:00

Author

Owner

@ejball commented on GitHub (Jul 3, 2020):

Do you mean for the markdownlint CLI and/or VS Code extension?

Yes, sorry about that; should I reopen this case at vscode-markdownlint and/or markdownlint-cli? Does one use the other, or are they independent? (My primary interest is in the VS Code extension.)

@ejball commented on GitHub (Jul 3, 2020): > Do you mean for the markdownlint CLI and/or VS Code extension? Yes, sorry about that; should I reopen this case at [vscode-markdownlint](https://github.com/DavidAnson/vscode-markdownlint) and/or [markdownlint-cli](https://github.com/igorshubovych/markdownlint-cli)? Does one use the other, or are they independent? (My primary interest is in the VS Code extension.)

kerem commented

2026-03-03 01:25:13 +03:00

Author

Owner

@DavidAnson commented on GitHub (Jul 3, 2020):

No worries! They are independent projects, though I own one and am a significant contributor for the other. I think this is most applicable for VS Code, but if there is history of CLI lint tools supporting this file, it would make sense there, too. Thanks!

@DavidAnson commented on GitHub (Jul 3, 2020): No worries! They are independent projects, though I own one and am a significant contributor for the other. I think this is most applicable for VS Code, but if there is history of CLI lint tools supporting this file, it would make sense there, too. Thanks!

kerem commented

2026-03-03 01:25:13 +03:00

Author

Owner

@ejball commented on GitHub (Jul 3, 2020):

Moved to https://github.com/DavidAnson/vscode-markdownlint/issues/120

@ejball commented on GitHub (Jul 3, 2020): Moved to https://github.com/DavidAnson/vscode-markdownlint/issues/120

kerem referenced this issue

2026-03-07 20:04:16 +03:00

[GH-ISSUE #259] Markdownlint links to old Rules.md documentation #2071