write-good VS vale

If you're using markdown, as a shameless plug, ThiefMD supports basic grammar checking, spell check, and English linting (passive voice detection, weasel words).

I like to use write-good[0] - it takes a glob and prints suggestions to stdout.

[0]: https://github.com/btford/write-good

write-good

btford/write-good – A naive linter for English prose.

Like most markdown editors, we have typewriter scrolling, focus mode, and live preview. Code Blocks support syntax highlighting for a majority of languages. We also have a selection of themes and support CSS for export formatting. Some of our secret sauce includes write-good suggestions based on btford's write-good, which we ported to Vala.

> Write in US English with US grammar. (Tested in British.yml.)

heh, that was funny but it turns out the file is a list of British words checked using Vale, which I just learned existed: https://github.com/errata-ai/vale#readme (MIT)

Also, another TIL is that the "e" version of gray is British https://gitlab.com/gitlab-org/gitlab/-/blob/master/doc/.vale... I had previously erroneously assumed they were just one of those quirks of English (which, I guess is still true but it is less random than I thought)

vale to spell check and enforce writing style on my articles

Similar to how a software has integration or unit tests that are built to make sure changes in the software don’t break the entire system, we implemented tests for our documentation’s style guide using Vale and ESLint.

Related: Vale is a plain-language or "prose" linter. Built a version of this for use with the US DVA

https://vale.sh/

For longer writing, I like using vale.

Hi r/Neovim! Today I released v0.2.0 for the [Tundra](https://github.com/sam4llis/nvim-tundra) theme so thought I’d post it here in case anybody is interested. ## Highlights: - Added `dim_inactive_windows` table in the Tundra `setup` function - when enabled, non-current windows will inherit the background colour `dim_inactive_windows.color`. - Added `:Tundra` command line sugar. This allows users to change configuration settings in real-time instead of having to reload their configuration. - `:Tundra toggle_transparency` - toggles `transparent_background` flag. - `:Tundra toggle_dim` - toggles `dim_inactive_windows.enabled` flag. - [nvim-treesitter](https://github.com/nvim-treesitter/nvim-treesitter) integration now requires Neovim 0.8. Obsolete `TS*` highlight groups were removed from nvim-treesitter and Tundra will no longer support older highlight groups. To use the obsolete highlight groups, downgrade to Tundra v0.1.0. See [this](https://github.com/nvim-treesitter/nvim-treesitter/pull/3656) for more information. - Support for common terminals and software including Alacritty, fzf, iTerm-2, WezTerm, and Windows Terminal. - Improvement of Tundra documentation. - Rewritten using [Vale](https://vale.sh) to keep a consistent style guide. You can find more information about the Tundra theme over at its [GitHub repository](https://github.com/sam4llis/nvim-tundra). Thanks for reading!

I like vale.sh, which is a commandline tool that lets you customize what checks you want done on your writing - basically a linter for prose. It looks like someone developed a flymake integration.

Can you add support for rule sets from https://vale.sh/ or to the vale itself?

I'm fond of Vale, where you can write your own rules or grab others off github. I wish we could crowd source a grammarly clone using it. Some efforts have been made to do so, but didn't get far.

https://github.com/errata-ai/vale

https://github.com/testthedocs/Openly