clangd VS Bear

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

There are generators for the compilation databases that work with Makefiles and other build systems, like Bear: https://github.com/rizsotto/Bear

Have you tried Bear? I used it for several projects and overall it works very well.

An update: I am now able to make everything work by generating `compile_commands.json` using compiledb. I'm aware that there is another tool Bear but for some reason it generates an empty `compile_commands.json` file for me.

Try https://github.com/rizsotto/Bear

Regarding the libraries, you might need to add it to clangd’s configuration. A convenient way is to have a compile_commands.json in your project (this is generated by some build tools like CMake, but if you don’t use them, have a look at bear).

Note that you need to have a compile_commands.json file. That file can easily be generated by CMake, Meson, etc. For other build systems checkout Bear https://github.com/rizsotto/Bear

make a 'gcc' command/executable that do nothing and make it first in your PATH and then run bear with make: https://github.com/rizsotto/Bear/issues/219 It is unfortunate that bear doesn't catch the output of the make command with '--dry-run' as it still prints the compile commands, it seems not that hard to support this and I think many ppl would benefit..

You could try to start with Bear: https://github.com/rizsotto/Bear In worst cases, I had to use strace to catch every gcc/g++ invocation and restructure the compile_commands.json out of the strace logs.

But it sounds like maybe you’re assuming for the purposes of using something like clangd (highly recommended for coding in cpp projects in general, you want to be using this in vscode or whatever else anyway, codelion notwithstanding I suppose) with neovim on a c++ project that you have to use cmake to produce a compilation database to use with neovim plugins (e.g. clangd via nvim-lsp et. al.). In this case, be aware that the https://github.com/rizsotto/Bear tool is a handy way to just tack it on to whatever command you’re using to run a c++ code build step, and it will give you a compile_commands.json, corresponding to the compiler commands it invoked, on a silver platter.