proselint VS markdownlint

So cool. Looks like the proseline site is down. For anyone else who wanted to read the approach - https://github.com/amperser/proselint/blob/b5b7536bec5fd461e...

You can try proselint, which also has built-in support in null-ls. Its LaTeX support isn't perfect, but it's workable.

Something like grammar-guard, proselint and/or language-tool?

Yep, though there's not a lot to see! Follow the instructions for installing proselint at https://github.com/amperser/proselint and configure as follows:

Vale uses a customizable grammar checker, and you can download some open-source configurations to start working with from the link above. Then, you just need to add something like below to your Emacs configuration: (flycheck-define-checker vale "A prose linter" :command ("vale" "--output" "line" source) :standard-input nil :error-patterns ((error line-start (file-name) ":" line ":" column ":" (id (one-or-more (not (any ":")))) ":" (message) line-end)) :modes (markdown-mode org-mode text-mode) ) (add-to-list 'flycheck-checkers 'vale 'append) (setq flycheck-vale-executable "/usr/local/bin/vale") It looks like you can do something similar with Proselint, which looks wonderful and I have been meaning to try using in my day-to-day: https://unconj.ca/blog/linting-prose-in-emacs.html .

proselint

Full list here. Since the tool is a linter, it sounds like it should work with language servers. I use CoC.nvim for LSP features. Thankfully some smart guys have figured out how to make proselint work with coc.nvim & coc-diagnostic (see here). Now it works for my blog posts just like clangd does for my C++ code.

You're looking for proselint. https://github.com/amperser/proselint

Some of Djot's features can be achieved by using markdownlint though: https://github.com/DavidAnson/markdownlint

markdownlint - A Node.js style checker and lint tool for Markdown/CommonMark files.

Improvements - The prefer-some-in-iteration rule will by default no longer flag iteration where a sub-attribute is used, like input[_].item - The use-in-operator rule has been extended to include more types of items, leading to better discovery of locations where in should be used - Remove replace directive in go.mod that made hard to integrate Regal as a library - The project now uses markdownlint to ensure consistent formatting of its documentation - The Go API now allows reading custom rules from an fs.FS filesystem

People are always looking for simple projects to learn Rust with, so here's one for anyone who's currently looking. Port markdownlint to Rust. Markdownlint is ~3.3k lines of JavaScript (including the lint implementation themselves!), so I reckon it's pretty doable.

The markdownlint VS Code extension is powered by the Node library of the same name. Its usage is quite similar to ESLint. It has a set of rules that can be configured, errors are highlighted, and you can automatically fix simple errors.

Markdown Lint

There are no compilers in the Flutter project that guarantee to find issues in README.md or CHANGELOG.md files. To remedy this, the Markdownlint plugin provides a set of guidelines to encourage Markdown file standards and uniformity. You can use this extension to check for problems locally and verify the content before publishing it live. Browse the user manual to learn more about rules.