Write Good Linter for Coc.nvim

Ported from vscode-write-good.

Because some APIs of vscode are missing in coc.nvim, disable some features temporarily:

• onDidChangeTextDocument: VS Code expect input is a TextDocument, coc.nvim expect input is a DidChangeTextDocumentParams. So it will lint when onDidSaveTextDocument and onDidOpenTextDocument, not onDidChangeTextDocument

Install

• coc-marketplace
• npm
• vim:

" command line
CocInstall coc-write-good
" or add the following code to your vimrc
let g:coc_global_extensions = ['coc-write-good', 'other coc-plugins']

Provides a write-good linter extension for Visual Studio Code.

Installation

Press F1 or CTRL+P (or CMD+P) and type out > ext install travisthetechie.write-good-linter. Check out the latest published version on the Visual Studio Marketplace.

Settings

write-good.languages defaults to ["markdown", "plaintext"], but it can be overridden to something like ["markdown"] if you would like linting to apply to other filetypes.

write-good.write-good-config is a direct pass through to the underlying write-good engine. To enable eprime check and disable check for so at the start of sentance, add "write-good.write-good-config": { "eprime": true, "so": false } to your settings.

write-good.only-lint-on-save disables linting during editing for large files. A save triggers linting.

write-good.debounce-time-in-ms is the minimum time, in milliseconds, that must wait between linting attempts. Saving ignores the minimum time. Default is 200ms. This is useful if linting causes any performance hit and you want to limit it.

License and acknowledgements

This is licensed under the MIT open source license. Do what you want with this software, just include notice that it orginated with me.

The heavy lifting of this extension is done via Brian Ford's write-good npm module.

Working on this project

Install Node.js & npm install in the project.

Open up the project in Visual Studio Code and hit F5 to open up a developement host version of Visual Studio Code with the extension installed. Open up a Markdown file and write some bad prose to see linter in action.

Check out the Extending Visual Studio Code documentation for more information.

Publishing

1. npm install -g vsce
2. Visit https://travisthetechie.visualstudio.com/_details/security/tokens for a token (all accounts, all scopes)
3. vsce login travisthetechie
4. vsce publish

Thank you to contributors

Thank you to James Ruskin for enabling settings. PR4

Thank you to Freed-Wu for typo fixes in configuration. PR22