mirror of
https://github.com/DavidAnson/markdownlint.git
synced 2026-04-25 09:16:02 +03:00
[GH-ISSUE #120] MD040 - fenced-code-language - Fenced code blocks should have a language specified #1950
Labels
No labels
bug
enhancement
enhancement
enhancement
fixed in next
fixed in next
fixed in next
new rule
new rule
new rule
pull-request
question
refactoring
refactoring
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/markdownlint#1950
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @V0d01ey on GitHub (May 8, 2018).
Original GitHub issue: https://github.com/DavidAnson/markdownlint/issues/120
Why the rule MD040 is introduced?
Why not using "code block" without syntax highlighting?
It is a simple useful marking for a preformatted text without indenting.
@DavidAnson commented on GitHub (May 8, 2018):
Correct syntax highlighting is usually clearer for the reader than without it, so this rule helps remind authors to add a language. If you do not want to do that, the rule can be disabled OR 4-space indenting can be used to create the code block instead.
@dhimmel commented on GitHub (Aug 27, 2019):
I always specify a language when there is one, but not sure what to specify when there is no corresponding language? For example, log output or help messages? Is there a language that can be specified which means no-syntax-highlighting?
@DavidAnson commented on GitHub (Aug 27, 2019):
@dhimmel, Usually “text” doesn’t do any highlighting.