python3 install.py --clangd-completer
:YcmDebugInfoshows "Server has Clang support compiled in: False" and "Clangd running", so I guess the C-family completer is correctly set to clangd-completer.
bearbut that probably won't work anymore
For an example of the utility of this script: after running
gen_compile_commands.json on the latest kernel version, I was able to
use Vim + the YouCompleteMe pluging + clangd to automatically jump to
definitions and declarations. Obviously, cscope and ctags provide some
Sometimes, after some hour of coding, in which I've certainly mashed TAB, I find out some file containing
#include <bits/stdc++.h>, which means that some TAB-completion triggered that. Since I discover this after a long time coding, typically when qualifying the change, I don't know which completion trigger that. Any idea which could it be? Plus, shouldn't that header be avoided, in general?
I've created this: https://github.com/clangd/clangd/issues/666#event-4251697760