Great extension! However I often make code fences in markdown, resulting in LOTS of false positive when vscode-spell-checker checks the code fence as if it was markdown code. Example:
````markdown
Bla bla this is markdown and all is good.
\usepackage[utf8]{inputenc}
```
which would result in warning onusepackageandinputenc`. Here is a screenshot that shows the issue:

The best solution would be to dynamically switch to the code fence language locally within the code fence.
The next-best solution would be to just ignore all content without code fences.
As a workaround, I have manually enabled the latex dictionary for the folder :)
It is possible to ignore those sections:
For all file types:
"cSpell.ignoreRegExpList": [
"/^```(?:.|\\s)+?^```/mig"
],
To have it apply only to markdown:
"cSpell.languageSettings": [
{
"languageId": "markdown",
"ignoreRegExpList": [
"/^```(?:.|\\s)+?^```/mig"
]
}
]
Thanks, can confirm it works to ignore content in code fences 馃憤
For inspiration, prettier.io actually implemented detection of language in code fences: https://prettier.io/blog/2018/04/11/1.12.0.html#support-fenced-codeblock-lang-followed-by-attributes-4153-https-githubcom-prettier-prettier-pull-4153-by-ikatyang-https-githubcom-ikatyang
Wanted behavior for markdown:
The current behavior is a nightmare for people writing technical stuff.
Else it generate too much false positive:
Plaintext code block:


Inline code:

Most helpful comment
It is possible to ignore those sections:
For all file types:
To have it apply only to markdown: