mirror of
https://github.com/DavidAnson/markdownlint.git
synced 2026-04-25 01:05:55 +03:00
[GH-ISSUE #1691] Incorrect warning when md is too long #734
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#734
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 @1298345095 on GitHub (Jul 25, 2025).
Original GitHub issue: https://github.com/DavidAnson/markdownlint/issues/1691
When text is short, there is no problem (split into multiple files)
Such as this:
Warning: MD018/no-missing-space-atx: No space after hash on atx style heading (Mistakenly identify #include as title)
And this:
MD010/no-hard-tabs: Hard tabs [Column: 1]
I already set "MD010":{
"ignore_code_languages": ["makefile"]
},
@DavidAnson commented on GitHub (Jul 25, 2025):
I don't understand what problem you are reporting - your scenario and example produce no warnings in the demo app:
https://dlaa.me/markdownlint/#%25m%23%20Issue%201691%0A%0A%60%60%60makefile%0Ahw%3A%20hw.o%20helper.o%0A%09gcc%20-o%20hw%20hw.o%20helper.o%20-lm%0Ahw.o%3A%20hw.c%0A%09gcc%20-O%20-Wall%20-c%20hw.c%0Ahelper.o%3A%20helper.c%0A%09gcc%20-O%20-Wall%20-c%20helper.c%0Aclean%3A%0A%09rm%20-f%20hw.o%20helper.o%20hw%0A%60%60%60%0A%0A%3C!--%20markdownlint-configure-file%20%7B%0A%20%20%22no-hard-tabs%22%3A%20%7B%0A%20%20%20%20%22ignore_code_languages%22%3A%20%5B%0A%20%20%20%20%20%20%22makefile%22%0A%20%20%20%20%5D%0A%20%20%7D%0A%7D%20--%3E%0A
@1298345095 commented on GitHub (Jul 25, 2025):
@DavidAnson commented on GitHub (Jul 25, 2025):
It looks like you quoted my own message back to me. Can you please demonstrate the problem, either in the demo page or by pointing to a repository or gist?
@1298345095 commented on GitHub (Jul 26, 2025):
No, I took the screenshot to show the line numbers, indicating that the issue occurs when there are many lines.
@1298345095 commented on GitHub (Jul 26, 2025):
You can create a markdown file with many lines to demonstrate the problem. When I finish the markdown, I will upload it to my repository.