David Anson

Related reading: - [History of `strict`](https://github.com/DavidAnson/markdownlint/issues/237) - [History of `stern`](https://github.com/DavidAnson/markdownlint/issues/256)

What I think you’ll find is that the first option, what I called “space” and what you don’t want at all is the default behavior in the Ruby (and therefore...

FYI, this is supported by the Node.js implementation: https://github.com/DavidAnson/markdownlint/blob/master/README.md#configuration There are test cases, etc., there to help ensure consistency.

In case it helps, here’s how this change looks in the Node.js implementation: https://github.com/igorshubovych/markdownlint-cli/commit/2640160aae2e285bc92074aa6893f192a278f7fd

Please see https://github.com/DavidAnson/markdownlint/commit/a2df7742c697c0261275ba808580bcfe72fa28d3 for how I handled this in the Node implementation (includes test cases).

To me, this rule is about preventing tabs, perhaps because they are handled inconsistently or may render poorly. Therefore, an option to enable tabs under some circumstances is an exceptional...

If folks would like to see how this is done in the Node implementation, you can play around here: https://dlaa.me/markdownlint/#%25m%23%20Demo%0A%0A1.%20%20%20%20%20List%20item%0A

FYI, the Node.js implementation offers automatic fixes for some rules: https://github.com/igorshubovych/markdownlint-cli/blob/master/README.md#fixing-errors

MD039 is only documented to detect spaces surrounding the link text: https://github.com/markdownlint/markdownlint/blob/master/docs/RULES.md#md039---spaces-inside-link-text

No strong feeling, just defending the current rule. :) I wonder if “no multiple spaces” makes sense as a more general rule that would apply here, in emphasis, headers, etc.?