languagetool-code-comments
null-ls.nvim
languagetool-code-comments | null-ls.nvim | |
---|---|---|
2 | 164 | |
31 | 3,554 | |
- | - | |
7.6 | 0.0 | |
3 months ago | 9 months ago | |
Rust | Lua | |
MIT License | GNU General Public License v3.0 or later |
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.
languagetool-code-comments
-
LanguageTool-Rust v2 releases 🎉: using LanguageTool grammar checker with Rust
languagetool-code-comments: uses LTRS to check for grammar errors within code comments
- [Release] languagetool-code-comments - Integrates the LanguageTool API to parse, spell check, and correct the grammar of your code comments!
null-ls.nvim
- cpp setting problem
-
Being a bash developer in the 21st century
you can use nvim then, it has shellcheck for diagnostics and formatting, like in vscode :)
here the link to the config: https://github.com/jose-elias-alvarez/null-ls.nvim/blob/main...
-
Linting/formatting and LSP
I use a lot of different languages generally and I'm running into issues around formatting. Is there any standard way to use LSP formatting by default and otherwise fallback to specific linter/formatting programs? I believe null-ls is the normal way of dealing with this, but since it's been archived, I'd rather not rely on it.
-
How to setup efm-langserver for pint formatter?
I've been using pint for formatting php files with null-ls.nvim. Few days ago null-ls.nvim has announced that the plugin will be archived in few months so I started migrating all my formatters and linter from null-ls to efm-langserver. I got other things such as prettier, black, isort, mypy, etc. working but can't get pint to work with php files: If I run pint via efm-langserver, everything is deleted from the buffer, and the saved file is formatted separately. How do I setup efm-langserver correctly to work with pint? Below is my config.yml for pint currently. yaml tools: pint: &pint format-command: "pint --no-interaction --quiet ${INPUT}" format-stdin: false languages: php: - <<: *pint Thank you.
- Archiving Null-Ls
- null-ls will be archived
-
Why is nobody using CoC anymore?
Because null-ls.nvim & mason.nvim together do everything I wanted CoC for
- Your favourite Neovim plugins?
-
How can I get yapf, black, and other formatters working with pylsp?
There is a good answer. I think you know lua and neovim config enough to pick things that you need. If you need a short answer, null-ls is the way.
What are some alternatives?
page - Use neovim as pager
formatter.nvim
moveline.nvim - Neovim plugin for moving lines up and down
nvim-lspconfig - Quickstart configs for Nvim LSP
vale - :pencil: A markup-aware linter for prose built with speed and extensibility in mind.
neoformat - :sparkles: A (Neo)vim plugin for formatting code.
nvim-send - Essentially "nvim --remote-expr <expr>" / "nvim --remote-send <keys>" or "nvr --nostart --remote-send <keys>" in Rust
StyLua - An opinionated Lua code formatter
languagetool-rust - LanguageTool API in Rust
nvim-lint - An asynchronous linter plugin for Neovim complementary to the built-in Language Server Protocol support.
watchexec - Executes commands in response to file modifications
efm-langserver - General purpose Language Server