clangd VS coc-diagnostic

I'm still waiting for clangd support, e.g. [0] before trying modules.

- [0] https://github.com/clangd/clangd/issues/1293

I know one way to do this, but hoping there's something simpler or more general. clangd (C++ LSP server) is over-aggressive about adding "helpful" #includes during completion. The way to turn that off is to pass -header-insertion=never on its cmd line.

Install the clangd language server using your system package manager, e.g. sudo apt-get install clangd

> As a side note, I despise things like imports and aliases. I'd prefer that when I do jump to a function, I can read it without having to check if anything is imported or not.

One idea might be to use an LSP (Language Server Protocol) interface. It could describe the fully qualified symbol for you when you, say, select the abbreviated symbol or press a keyboard shortcut. I've been working on a moderately large C program with Emacs and clangd[1] recently and have been amazed at how 'immersive' it feels, and that's from someone who's used to the comfort of a Lisp REPL!

[1]: https://clangd.llvm.org/

FWIW, recent clangd also has this feature: "unused" as of 14, "missing" as of 16, works better in snapshots.

You need to install CMake (and use it to build your project - which you should do in any case) and clangd.

First we would need the Clangd extension as well as the LSP itself You can download the extension from #here The extension provides its own Clangd LSP but in case of issues with that we would like to download and setup the clangd package from the official site for both Windows and Linux I daily drive Linux on my laptop, thus this guide works well for linux users, Windows users can use programs like Cygwin to replicate the process

Few days ago I found a bug while using clangd LSP with neovim, and submitted a bug report to clangd: https://github.com/clangd/clangd/issues/1640

Come to the light side: VSCodium with clangd

If you use the clangd LSP: https://github.com/clangd/clangd/issues

More specifically, i use coc-diagnostic extension , with the default configuration for python linting as advised in coc-jedi-lint repo .

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.

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.