[GH-ISSUE #251] MD037 - Multiple errors of MD037 in a single line is not being fixed at once. #216

New issue

Closed

opened 2026-03-03 01:24:45 +03:00 by kerem · 4 comments

kerem commented

2026-03-03 01:24:45 +03:00

Owner

Originally created by @satishdsc on GitHub (Jan 28, 2020).
Original GitHub issue: https://github.com/DavidAnson/markdownlint/issues/251

Le **This is test Management ** testing purpose only **Configuration test ** > **test ** > **test d'admin ** > Configuration **test ** test **Configuration test ** > **test ** > **Admin Modèles ** > **Composants test **.

@DavidAnson
All MD037 issues are detected in the above statement. I have configured to fix these issues on save. When I save, only 1 issue is fixed. So, I have to hit 'save' 5 times to fix all of them. And on the fifth time, the extension shows all have been fixed. However, some issues are not fixed and not linted as well after hitting save several times. For example, these **This is test Management ** testing purpose only **Configuration test ** > **test ** > **test d'admin ** > issues are not fixed.

Originally created by @satishdsc on GitHub (Jan 28, 2020). Original GitHub issue: https://github.com/DavidAnson/markdownlint/issues/251 `Le **This is test Management ** testing purpose only **Configuration test ** > **test ** > **test d'admin ** > Configuration **test ** test **Configuration test ** > **test ** > **Admin Modèles ** > **Composants test **.` @DavidAnson All MD037 issues are detected in the above statement. I have configured to fix these issues on save. When I save, only 1 issue is fixed. So, I have to hit 'save' 5 times to fix all of them. And on the fifth time, the extension shows all have been fixed. However, some issues are not fixed and not linted as well after hitting save several times. For example, these `**This is test Management ** testing purpose only **Configuration test ** > **test ** > **test d'admin ** >` issues are not fixed.

kerem

2026-03-03 01:24:45 +03:00

closed this issue
added the
enhancement

fixed in next
labels

kerem commented

2026-03-03 01:24:46 +03:00

Author

Owner

@DavidAnson commented on GitHub (Jan 28, 2020):

Is the example above supposed to be one long line? The “>” characters look like they might be used as block quote markers.

@DavidAnson commented on GitHub (Jan 28, 2020): Is the example above supposed to be one long line? The “>” characters look like they might be used as block quote markers.

kerem commented

2026-03-03 01:24:46 +03:00

Author

Owner

@satishdsc commented on GitHub (Jan 30, 2020):

@DavidAnson The example is like small paragraph with multiple lines. This paragraph kind of describes on how to navigate to a particular menu or take same action. So the character ">" is used to show the navigation sequence. For example To navigate to settings click on **Home** > **my profile** > **settings**. So, I think when we try fix the MD037 issue on this example, space is being removed between ** and > whereas the space between ** and the text should be removed.

@satishdsc commented on GitHub (Jan 30, 2020): @DavidAnson The example is like small paragraph with multiple lines. This paragraph kind of describes on how to navigate to a particular menu or take same action. So the character ">" is used to show the navigation sequence. For example `To navigate to settings click on **Home** > **my profile** > **settings**`. So, I think when we try fix the MD037 issue on this example, space is being removed between ** and > whereas the space between ** and the text should be removed.

kerem commented

2026-03-03 01:24:46 +03:00

Author

Owner

@DavidAnson commented on GitHub (Jan 31, 2020):

In the first original example, only 2 issues are identified; it takes 5 rounds of fixing to address everything.

In the second original example, I see 2 issues identified; 2 rounds of fixing address everything.

I'll look into this scenario because it seems the library could be doing better at detection - but will caution folks that there will always be scenarios that confound the tool - simply because it's having to deal with behavior that violates the specification and figure out what the user probably meant. Note that for both examples, VS Code's Markdown preview doesn't render anything in bold despite the overwhelming number of "**"'s.

@DavidAnson commented on GitHub (Jan 31, 2020): In the first original example, only 2 issues are identified; it takes 5 rounds of fixing to address everything. In the second original example, I see 2 issues identified; 2 rounds of fixing address everything. I'll look into this scenario because it seems the library could be doing better at detection - but will caution folks that there will always be scenarios that confound the tool - simply because it's having to deal with behavior that violates the specification and figure out what the user probably meant. Note that for both examples, VS Code's Markdown preview doesn't render anything in bold despite the overwhelming number of "**"'s.

kerem commented

2026-03-03 01:24:46 +03:00

Author

Owner

@satishdsc commented on GitHub (Jan 31, 2020):

Yes thank you.

@satishdsc commented on GitHub (Jan 31, 2020): Yes thank you.

kerem referenced this issue

2026-03-07 20:03:53 +03:00

[GH-ISSUE #216] Trailing whitespace that could produce a hard break but won't due to context should also be flagged by MD009 #2034