David Anson

This isn't implemented because it requires a single fix that touches both the open and close of the fence (different lines) and that is not easily possible today. It will...

As I understand the specification you link to, there are a few differences: - Translation of header text is different, notably for accented characters. - Nested headings generate unique identifiers...

@scottamain Please do. I think supporting named anchors is more straightforward and has value in isolation.

That's really neat, I love it!! It's not a "normal" rule like the existing MD### rules, so my current thinking is to leave it separate. (I see it's already tagged...

I am happy to include a link to this rule from the documentation! If you'd like to send a PR, I expect to publish a new release soon, and it...

@OnkarRuikar The “selectively disable part of a rule” proposal feels weird and special-case to me. I think a more general approach might be to allow reconfiguring a rule inline, but...

I am proposing a new "meta-rule" which exports an array of multiple instances of the existing rule like you show (already supported today). Each name would need to be unique,...

Regarding splitting configuration, it looks like you have about eight different definitions in the file you link to. In the extreme, you could give each one its own instance of...

Actually, the name "meta-rule" is a bad choice on my part. A single file can export multiple rules in an array. That's all I'm suggesting. Each one of those would...

Smart!!! (Just curious, why do you need to bind vs. calling rule.function with the modified params directly?