starred/markdownlint

Fork 0

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

[GH-ISSUE #15] CommonMark mention #10

New issue

Closed

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

kerem commented

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

Owner

Originally created by @igorshubovych on GitHub (Mar 10, 2016).
Original GitHub issue: https://github.com/DavidAnson/markdownlint/issues/15

Currently README.md call markdownlint A Node.js style checker and lint tool for Markdown files.

Should CommonMark be mentioned too?

As far as I understood it covers CommonMark pretty good. CommonMark nowadays is becoming a de-facto standard, because it has spec unlike Markdown. I see that you included link to this spec in README.md.

Originally created by @igorshubovych on GitHub (Mar 10, 2016). Original GitHub issue: https://github.com/DavidAnson/markdownlint/issues/15 Currently README.md call markdownlint `A Node.js style checker and lint tool for Markdown files`. Should CommonMark be mentioned too? As far as I understood it covers CommonMark pretty good. CommonMark nowadays is becoming a de-facto standard, because it has spec unlike Markdown. I see that you included link to this spec in README.md.

kerem

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

closed this issue
added the
enhancement
label

kerem commented

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

Author

Owner

@DavidAnson commented on GitHub (Mar 10, 2016):

Makes sense! As you say, the markdown-it parser is CommonMark-compliant. Because CommonMark is a dialect/subset of Markdown, maybe something like the following:

A Node.js style checker and lint tool for Markdown/CommonMark files.

@DavidAnson commented on GitHub (Mar 10, 2016): Makes sense! As you say, the `markdown-it` parser is CommonMark-compliant. Because CommonMark is a dialect/subset of Markdown, maybe something like the following: > A Node.js style checker and lint tool for Markdown/CommonMark files.

kerem commented

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

Author

Owner

@igorshubovych commented on GitHub (Mar 10, 2016):

Well, honestly I am not sure. Need to double check.

@igorshubovych commented on GitHub (Mar 10, 2016): Well, honestly I am not sure. Need to double check.

kerem commented

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

Author

Owner

@igorshubovych commented on GitHub (Mar 10, 2016):

http://talk.commonmark.org/t/is-commonmark-really-markdown-compatible/540

@igorshubovych commented on GitHub (Mar 10, 2016): http://talk.commonmark.org/t/is-commonmark-really-markdown-compatible/540

kerem commented

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

Author

Owner

@DavidAnson commented on GitHub (Mar 11, 2016):

Lots of strong opinions there. :) My proposal above deliberately does not take sides. "Markdown/CommonMark" suggests that both are supported without saying one is better or a subset, etc..

Until the day we find a rule that needs to behave differently, this may be good enough.

@DavidAnson commented on GitHub (Mar 11, 2016): Lots of strong opinions there. :) My proposal above deliberately does not take sides. "Markdown/CommonMark" suggests that both are supported without saying one is better or a subset, etc.. Until the day we find a rule that needs to behave differently, this may be good enough.

kerem commented

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

Author

Owner

@DavidAnson commented on GitHub (Mar 11, 2016):

BTW, the title on the page http://commonmark.org/ says the following which is what I based my phrase "dialect/subset" on:

CommonMark - A strongly defined, highly compatible specification of Markdown

@DavidAnson commented on GitHub (Mar 11, 2016): BTW, the title on the page http://commonmark.org/ says the following which is what I based my phrase "dialect/subset" on: > CommonMark - A strongly defined, highly compatible specification of Markdown

kerem commented

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

Author

Owner

@igorshubovych commented on GitHub (Mar 11, 2016):

CommonMark - A strongly defined, highly compatible specification of Markdown

Then it should be ok to have Markdown/CommonMark

@igorshubovych commented on GitHub (Mar 11, 2016): > CommonMark - A strongly defined, highly compatible specification of Markdown Then it should be ok to have Markdown/CommonMark

kerem commented

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

Author

Owner

@DavidAnson commented on GitHub (Mar 11, 2016):

Great - I'll make the update soon.

@DavidAnson commented on GitHub (Mar 11, 2016): Great - I'll make the update soon.

kerem referenced this issue

2026-03-07 20:02:08 +03:00

[GH-ISSUE #10] Maximum line width #1853