mirror of
https://github.com/DavidAnson/markdownlint.git
synced 2026-04-25 17:26:22 +03:00
[GH-ISSUE #294] Fix is not fixing line_length #250
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#250
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 @wtrocki on GitHub (Jun 4, 2020).
Original GitHub issue: https://github.com/DavidAnson/markdownlint/issues/294
markdownlint ./docs/**/*.md --fix
Getting issues about lines but they aren't fixed
@DavidAnson commented on GitHub (Jun 4, 2020):
Not all rules are fixable. I have a note to call this out explicitly in the rule documentation, but for now you can find a list here: https://github.com/DavidAnson/vscode-markdownlint/blob/master/README.md#rules
In particular, line length is not automatically fixed because there are many cases where it won’t be clear to a tool what to change to reflow a paragraph, etc.. This is a feature many editors support and I recommend addressing line length issues that way.
@DavidAnson commented on GitHub (Jun 22, 2020):
Fixable rules are now called out in the documentation by
github.com/DavidAnson/markdownlint@53a0ba18d8for the next release.@virtzilla commented on GitHub (Aug 22, 2025):
It would be incredibly useful to show in the output of the command (i.e. a prefix or suffix of "NOT FIXED" or "CAN'T FIX") on what isn't fixed rather than having to hunt down in the documentation to find it's behaving as designed and it's not a bug that it didn't fix it (after trying repeatedly way more times than I care to admit).