coc-diagnostic
diagnostic-languageserver
coc-diagnostic | diagnostic-languageserver | |
---|---|---|
3 | 16 | |
244 | 405 | |
- | - | |
5.5 | 1.6 | |
7 months ago | 3 months ago | |
TypeScript | TypeScript | |
- | MIT License |
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.
coc-diagnostic
-
Configure autocompletion refresh in CoC nvim
More specifically, i use coc-diagnostic extension , with the default configuration for python linting as advised in coc-jedi-lint repo .
-
Vim - Using clippy as a linter
I'm currently using vim + coc + coc-diagnostic + rust-analyzer for all my Rust dev work. Clippy is very helpful and I'd like to configure Vim to give me inline suggestions from Clippy.
-
Setting up VIM for blogging
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.
diagnostic-languageserver
-
Vim - Using clippy as a linter
I'm not using the rust-analyzer plugin actually. I'm using the system installed rust-analyzer and diagnostic-language-server which integrates it with vim. Is there a flag or something to make rust-analyzer return clippy results as well?
-
diagnosticls-configs-nvim - pre-defined linter and formatter configs for diagnostic-languageserver
For those who use diagnostic-languageserver, this plugin provides a list of pre-defined configurations for you to use without the hassle to figure out the config on your own. Making it easier to integrate with less code.
- How to determine which linter is currently being used?
-
Eslint Lua Solution?
So reading through everyones suggestions it seems like diagnosticls is the way to go. Looks like this is the official neovim solution https://github.com/iamcco/diagnostic-languageserver formerly https://github.com/nvim-lua/diagnostic-nvim
-
Config to edit bash scripts with fancy LSP features, linting and formatting
Does anybody have such? Maybe you could share your experience? I use coc.nvim. My eyes fell on these 3 tools. The first one is language server and it has coc extensions coc-sh. But others are not so I am not sure which vim plugin should I use to hook them up: besides diagnostic-languageserver there are syntastic and neomake - bash-language-server - shellcheck - shfmt
-
Neovim LSP and typescript
>https://github.com/iamcco/diagnostic-languageserver
-
TypeScript: ESLint code actions and (experimental) diagnostics / formatting
I also added 2 experimental features designed to reduce the amount of boilerplate required to get a functional TypeScript development environment. diagnostic-languageserver and efm-langserver are powerful, but they can be tough to set up for new users, so I wanted to implement low-config, out-of-the-box alternatives for formatting and linting:
-
Losing my mind with formatting
I’ve personally never gotten efm to work at all, and I never figured out why (much like your situation). I use diagnostic-languageserver, which worked like a charm the first time. I’ve heard some users say it’s slower (TypeScript versus Go), but I’ve never had any speed issues.
-
Neovim - Why I'm switching to Native LSP over CoC
Aside from that, the biggest difference versus CoC is the ecosystem, which affects setup / tweaking time and code actions. I was able to set up ESLint diagnostics with diagnostic-languageserver, but it doesn't integrate with typescript-language-server at all, and I haven't been able to set up ESLint fixing + Prettier, either, All of that is trivial with CoC.
-
LSP and pylama…
Some LSP like diagnostic language server and efm language server do that for you. However, you will need to do some manual setup yourself for pylama to work with them, unfortunately, I don't see either of them have an example for pylama so you will have to write one yourself for those LSP servers.
What are some alternatives?
clangd - clangd language server
null-ls.nvim - Use Neovim as a language server to inject LSP diagnostics, code actions, and more via Lua.
proselint - A linter for prose.
nvim-lspconfig - Quickstart configs for Nvim LSP
coc-ccls - CCLS (C/C++) extension for coc.nvim
efm-langserver - General purpose Language Server
vim-autocorrect - Correct common typos and misspellings as you type in Vim
coc-spell-checker - A basic spell checker that works well with camelCase code for (Neo)vim
coc.nvim - Nodejs extension host for vim & neovim, load extensions like VSCode and host language servers.
neomake - Asynchronous linting and make framework for Neovim/Vim
coc-rust-analyzer - rust-analyzer extension for coc.nvim
syntastic - Syntax checking hacks for vim