[GH-ISSUE #389] [feature request] disable for next block #2173

New issue

Closed

opened 2026-03-07 20:05:15 +03:00 by kerem · 2 comments

kerem commented

2026-03-07 20:05:15 +03:00

Owner

Originally created by @CircleCode on GitHub (Apr 23, 2021).
Original GitHub issue: https://github.com/DavidAnson/markdownlint/issues/389

Say i want to enforce MD013 for all code blocks, except one (for example, I show raw script output, and I want it be unaltered)

I'd like to have something like

<!-- markdownlint-disable-next-block MD013 -->
```raw
some text with very long lines
[…]
```

Originally created by @CircleCode on GitHub (Apr 23, 2021). Original GitHub issue: https://github.com/DavidAnson/markdownlint/issues/389 Say i want to enforce MD013 for all code blocks, except one (for example, I show raw script output, and I want it be unaltered) I'd like to have something like `````md  ```raw some text with very long lines […] ``` `````

kerem

2026-03-07 20:05:15 +03:00

closed this issue
added the
enhancement
label

kerem commented

2026-03-07 20:05:17 +03:00

Author

Owner

@CircleCode commented on GitHub (Apr 23, 2021):

after a more attentive reading, I was able to fulfill my needs with

<!-- markdownlint-capture -->
<!-- markdownlint-disable MD013 -->
```raw
some text with very long lines
[…]
```
<!-- markdownlint-restore -->

However, i do not close this issue because I think a per block exception would make sense for readibility.
But if you consider this is too much work compared to the real benefit, feel free to close this request

@CircleCode commented on GitHub (Apr 23, 2021): after a more attentive reading, I was able to fulfill my needs with `````md   ```raw some text with very long lines […] ```  ````` However, i do not close this issue because I think a *per block exception* would make sense for readibility. But if you consider this is too much work compared to the real benefit, feel free to close this request

kerem commented

2026-03-07 20:05:17 +03:00

Author

Owner

@DavidAnson commented on GitHub (Apr 23, 2021):

I agree that would be a little more elegant, but it adds complexity and assumes people know what a block is (maybe less clear with text vs. code?). I'll keep this in the back of my mind, but for now will stick with the pattern you show above. Thanks for the suggestion, glad you figure this out!

@DavidAnson commented on GitHub (Apr 23, 2021): I agree that would be a little more elegant, but it adds complexity and assumes people know what a block is (maybe less clear with text vs. code?). I'll keep this in the back of my mind, but for now will stick with the pattern you show above. Thanks for the suggestion, glad you figure this out!