[GH-ISSUE #139] "MD010 - Hard tabs" - ignore for code fences? #118

New issue

Closed

opened 2026-03-03 01:23:53 +03:00 by kerem · 4 comments

kerem commented

2026-03-03 01:23:53 +03:00

Owner

Originally created by @gandalfsaxe on GitHub (Jul 31, 2018).
Original GitHub issue: https://github.com/DavidAnson/markdownlint/issues/139

Hi,

If I'm having a code fence in markdown for a language that may contain tabs, markdownlink shouldn't mark this with a MD010 warning? Because it's not markdown, it's a "quote" of another programming language that perhaps may contain tabs.

E.g. this .gitattributes content have tabs and that's fine:

*               text=auto
*.txt		text
*.vcproj	text eol=crlf
*.sh		text eol=lf
*.jpg		-text

Originally created by @gandalfsaxe on GitHub (Jul 31, 2018). Original GitHub issue: https://github.com/DavidAnson/markdownlint/issues/139 Hi, If I'm having a code fence in markdown for a language that may contain tabs, markdownlink shouldn't mark this with a MD010 warning? Because it's not markdown, it's a "quote" of another programming language that perhaps may contain tabs. E.g. this `.gitattributes` content have tabs and that's fine: ``` * text=auto *.txt text *.vcproj text eol=crlf *.sh text eol=lf *.jpg -text ```

kerem

2026-03-03 01:23:53 +03:00

closed this issue
added the
question
label

kerem commented

2026-03-03 01:23:54 +03:00

Author

Owner

@DavidAnson commented on GitHub (Jul 31, 2018):

You want to set the code_blocks parameter of MD010 to false: https://github.com/DavidAnson/markdownlint/blob/master/doc/Rules.md#md010

@DavidAnson commented on GitHub (Jul 31, 2018): You want to set the `code_blocks` parameter of MD010 to `false`: https://github.com/DavidAnson/markdownlint/blob/master/doc/Rules.md#md010

kerem commented

2026-03-03 01:23:54 +03:00

Author

Owner

@gandalfsaxe commented on GitHub (Jul 31, 2018):

Ah sorry, didn't know how I overlooked that. Curious, why is the default true?

@gandalfsaxe commented on GitHub (Jul 31, 2018): Ah sorry, didn't know how I overlooked that. Curious, why is the default true?

kerem commented

2026-03-03 01:23:54 +03:00

Author

Owner

@DavidAnson commented on GitHub (Aug 1, 2018):

In my experience, tabs are handled differently by many tools. So I would prefer not to have any in my document which should lead to the most predictable behavior. But for scenarios where tabs are wanted in code, this option lets you allow them.

@DavidAnson commented on GitHub (Aug 1, 2018): In my experience, tabs are handled differently by many tools. So I would prefer not to have any in my document which should lead to the most predictable behavior. But for scenarios where tabs are wanted in code, this option lets you allow them.

kerem commented

2026-03-03 01:23:54 +03:00

Author

Owner

@gandalfsaxe commented on GitHub (Aug 1, 2018):

I see. Thanks for the elaboration.

On 1 Aug 2018, at 02.53, David Anson notifications@github.com wrote:

In my experience, tabs are handled differently by many tools. So I would prefer not to have any in my document which should lead to the most predictable behavior. But for scenarios where tabs are wanted in code, this option lets you allow them.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

@gandalfsaxe commented on GitHub (Aug 1, 2018): I see. Thanks for the elaboration. > On 1 Aug 2018, at 02.53, David Anson <notifications@github.com> wrote: > > In my experience, tabs are handled differently by many tools. So I would prefer not to have any in my document which should lead to the most predictable behavior. But for scenarios where tabs are wanted in code, this option lets you allow them. > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub, or mute the thread.

kerem referenced this issue

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

[GH-ISSUE #118] feature_request(configuration): support YAML configuration format #1947