facelessuser
commented
3 years ago Are you spell checking raw Markdown or are you converting it to HTML and then checking the HTML?
Often, I convert Markdown to HTML and then use CSS selectors to ignore code blocks and such. It is often easier for me to filter things in HTML. That is my general recommendation, but there are potentially other ways. PySpelling, which is used to filter the content, has a Markdown filter which basically converts the Markdown content to HTML. The HTML filter allows you to filter out tags with selectors. Granted, you must enable an extension to handle fenced code properly though as fenced code is not part of the spec (old school spec, I'm not sure about CommonMark).
The shipped extension that handles Markdown uses Python Markdown, which is an old school Markdown parser (not a CommonMark parser). For me, that is more than sufficient for my needs as the documentation I am often parsing also uses Python Markdown when I publish the documentation. If CommonMark is a requirement, a 3rd party extension can surely be created .
I can't really answer further without out knowing how you are attempting to spell check your Markdown.
supernovae
jonasbn
byronmiller
Is it possible to tell spellcheck to ignore the markdown hinted areas for language?
For example, if I have
```bash kubectl get nodes ```
Can it just not spellcheck that bash statement? I have lots of awscli or kubectl or curl commands and right now that means 800+ misspelled words