Openly
vscode-ltex
Our great sponsors
- InfluxDB - Access the most powerful time series database as a service
- ONLYOFFICE ONLYOFFICE Docs — document collaboration in your environment
- SonarQube - Static code analysis for 29 languages.
- CodiumAI - TestGPT | Generating meaningful tests for busy devs
| Openly | vscode-ltex | |
|---|---|---|
| 4 | 9 | |
| 116 | 653 | |
| -0.9% | - | |
| 0.0 | 0.0 | |
| 2 months ago | 23 days ago | |
| Gherkin | TypeScript | |
| MIT License | Mozilla Public License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Openly
-
Writing like a pro with Vale and Neovim
They don't mention that can write the rules yourself and also pick and choose from existing rules from github.
There is an attempt to build and open source version of grammarly using vale rules here.
-
A little grammar help, anyone?
Check out Openly (https://github.com/testthedocs/Openly) -- it's a "Vale linter style that attempts to emulate some features of the commercial, and closed source, Grammarly."
-
Markdown Linting
Grammarly Clone in Vale
-
"Stealing" style guide content
There's even a project of someone trying to simulate Grammarly, although it looks a bit dead right now: https://github.com/testthedocs/Openly
vscode-ltex
-
What would be the best way to run Grammarly on a latex file?
In case you do not insist on using Grammarly, you can use LanguageTool (offline) via the LTeX plugin.
-
What external tools do you use in your workflow?
As a philosophy student: Zotero for reference management, the Better BibTeX plugin to auto-generate a .bib file, and two language servers for diagnostics: LTeX for grammar- and spellchecking, and alex for style and sensitivity checking.
-
Write Better in Neovim With Languagetool
If you use VS Code, you can use the extension vscode-ltex.
ltex-ls
- Writing like a pro with Vale and Neovim
-
Setup your private LanguageTool server
If you want language-tool support for your markdown files within vscode you can use the LTEX Extension.
- Otter.ai has saved reporters hours transcribing interviews. Caveat emptor
What are some alternatives?
languagetool - Style and Grammar Checker for 25+ Languages
coc-spell-checker - A basic spell checker that works well with camelCase code for (Neo)vim
coc-prettier - Prettier extension for coc.nvim.
coc-explorer - 📁 Explorer for coc.nvim
vale-styles - Checks for Vale based on popular style guides
cspell - A Spell Checker for Code!
docs - Linode guides and tutorials.
vale - :pencil: A syntax-aware linter for prose built with speed and extensibility in mind.
traefik - The Cloud Native Application Proxy
mp4grep - mp4grep is a CLI for transcribing and searching audio/video files
write-good - Naive linter for English prose
Vale - Compiler for the Vale programming language - http://vale.dev/