HTML disable/enables comments triggered when inside Markdown inline code about markdownlint

[DavidAnson]

If you scroll down a bit in the README, it says there is an implicit capture at the top of every document. It's not wrong to pair every restore with a capture, but it's unnecessary if nothing has been disabled or enabled up to that point.

[DavidAnson]

I think your lookbehind got garbled, but I'd be reluctant to "fix" this too narrowly as there is no guarantee the backticks are tight to the comment (or that nothing else is in between).

What do you think about this approach that works today: https://dlaa.me/markdownlint/#%25m%23%20Issue%201213%0A%0AText%20%60%3C!--%20markdownlint-disable%20--%3E%60%20text%0A%0A%3C!--%20markdownlint-restore%20--%3E%0A%0A%23%20Extra%20H1%0A

[rachmari]

@DavidAnson sorry for the typo in the issue summary. There was an extra ` (Fixed).

What do you think about this approach that works today:

I didn't know about the restore config option. Does this option restore back to the rule configuration prior to any disables/enables? I see the description in the README, but it's not clear whether it restores back to the captured configuration. It seems to imply that the restore option must be used only after the capture option is used. Is that accurate?

[rachmari]

@DavidAnson thank you for the explanation. In that case, the solution you provided does work for us. Thank you! ✨