[GH-ISSUE #294] Fix is not fixing line_length #250

Closed
opened 2026-03-03 01:25:08 +03:00 by kerem · 3 comments
Owner

Originally created by @wtrocki on GitHub (Jun 4, 2020).
Original GitHub issue: https://github.com/DavidAnson/markdownlint/issues/294

{
    "line_length": 120
}

markdownlint ./docs/**/*.md --fix

Getting issues about lines but they aren't fixed

Originally created by @wtrocki on GitHub (Jun 4, 2020). Original GitHub issue: https://github.com/DavidAnson/markdownlint/issues/294 ``` { "line_length": 120 } ``` markdownlint ./docs/**/*.md --fix Getting issues about lines but they aren't fixed
kerem 2026-03-03 01:25:08 +03:00
  • closed this issue
  • added the
    question
    label
Author
Owner

@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.

<!-- gh-comment-id:639012664 --> @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.
Author
Owner

@DavidAnson commented on GitHub (Jun 22, 2020):

Fixable rules are now called out in the documentation by github.com/DavidAnson/markdownlint@53a0ba18d8 for the next release.

<!-- gh-comment-id:647591774 --> @DavidAnson commented on GitHub (Jun 22, 2020): Fixable rules are now called out in the documentation by https://github.com/DavidAnson/markdownlint/commit/53a0ba18d847cd49952f5626ac700189a821ce99 for the next release.
Author
Owner

@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).

<!-- gh-comment-id:3214966662 --> @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).
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/markdownlint#250
No description provided.