Ignore VS Code default exclusions

Hey, I notice that createFileSystemWatcher does not allow for inserting the list of default VS Code exclusions unlike for example findFiles with its exclude argument you can set to undefined to make it use the default built-in excludes. That means currently this extension reports errors from even node_modules and such and in my case that blows some of my projects up to thousands of errors. You might want to consider trying to somehow extract this exclusion list from VS Code and adjusting your glob (either statically or even better dynamically based on the exclusion list) to ignore these.

[DavidAnson]

More FYI, @chrmarti kindly opened an issue for VS Code to look into this: https://github.com/Microsoft/vscode/issues/50874

What we’re seeing may not be entirely expected.

[DavidAnson]

Looking at VS Code on my machine, I see the following behavior (always re-open the folder when testing).

Prevents linting *.md from vendor directory, but hides directory in explorer:

"files.exclude": {
    "**/vendor": true
},

Does not exclude *.md from vendor directory:

"search.exclude": {
    "**/vendor": true
}

Also does not exclude:

"files.watcherExclude": {
    "**/vendor/*/**": true
},

Which brings me back to suggesting markdownlint.ignore.

Prevents linting *.md from vendor directory, no effect on explorer, no effect on Ctrl+T:

"markdownlint.ignore": [
    "vendor/**"
]

Code-wise, I confirm that VS Code’s handling of Ctrl+T is to invoke vscode.workspace.onDidOpenTextDocument for every Markdown document it scans. There is no matching call to vscode.workspace.onDidCloseTextDocument. Either or both may be a bug.

I can’t yet see a way to tell the Ctrl+T scenario apart from the normal document open scenario from the extension’s code.

markdownlint.ignore seems to be the ideal solution for now.