David Anson

This seems like it will be more of a heuristic than an absolute - I'm going to make it a new rule so it can be disabled independently of `MD030`....

Wow, thanks! I just found out about that a couple of days ago. After skimming the docs, I added it to my (long) list of things to learn more about....

Cool. I have a migration plan to get to Web Crypto and it looks like this can help. :) Really appreciate the pointers!

This should work in the next update, via https://github.com/DavidAnson/markdownlint/commit/ffc4d569182a116c0233b2efc97353364c470702.

Today, global configuration is relative to home directory as you outline. Something like what you propose seems like a reasonable enhancement, especially if there is precedence in VS Code already.

You'd probably want something like `${workspaceFolder}`, though it looks like this is not broadly supported in Settings: https://code.visualstudio.com/docs/editor/variables-reference#_is-variable-substitution-supported-in-user-and-workspace-settings

This is what the `siblings_only` parameter is for. There is an example of your scenario in the documentation for this rule: https://github.com/DavidAnson/markdownlint/blob/main/doc/Rules.md#md024

A bit of context first, apologies if you know all of this already... Briefly, this extension acts on files that VS Code identifies as using the "markdown" language. It seems...

My lesser worry is having to update code action provider registration dynamically if language became configurable: https://github.com/DavidAnson/vscode-markdownlint/blob/4d9d81ea6c864c0fd4a7d5479769f41daa837929/extension.js#L960 My bigger worry is that configuring an extension to properly get loaded when...

@tarensanders What extension do you use to provide RMD support in VS Code? I have an idea how to do solve this by adding the .RMD extension to the markdown...