David L. Day

[markdownlint](https://github.com/DavidAnson/markdownlint#configuration) provides a good example.

Actually, both Markdown and HTML support HTML Comments, so using the same approach for both will simplify the code, at least for now.

Hey! Thanks for opening an issue, and sorry about the long delay. Was on an extended vacation. I'll take a look as soon as I can.

@chrillek - I'm unable to recreate the issue with either the Markdown document or "A simple test" in a plain text file. I'm running LT v5.8 via podman locally. Are...

Thanks for uncovering this! I'll incorporate something to prevent this from happening to others.

The warning is only for when using the Public API provided by LanguageTool. If you're using an external or managed service, you can safely ignore that warning and enable "Lint...

Not sure what you mean by "normal" VSC command, so is there something more you're asking for? It should also be in the command palette under the "LanguageTool Linter" prefix.

It's not there because the linter doesn't recognize the format of the document you have open. That's why you get the "Force Check as Plain Text Document". If you open...

I see what you're saying. Since you've added `asciidoc` as a plain text id, you would like to see the same command you see for the supported language ids (i.e....

I've relabeled as a document update. Thank you for the feedback!