I saw in the main page video that you seem to have gotten clangd to work perfectly. Any tips. I got ccls to work perfectly.

[FranckKernel]

Hi, I saw that your lsp is perfectly setup, and the completion style reminds me more of clangd then ccls.
I keep getting false positive linting errors, and imperfect function override resolution and others with clangd.

Or you are using ccls and the autocomplete style is exactly the same as my clangd autocomplete style.

Anyway, a bit of help and tips would be appreciated.
Thanks, have a good day and thanks for the plugin.

[anurag3301]

In my experience, neither of them is perfect but I have had better experince with ccls, but I do keep switching between them. I recommend you try both too, for ccls just run pio init --ide vim which will generate a .ccls file, for clangd run pio run -t compiledb which will generate compile_commands.json

Now unnecessary compiler diagnostic error is expected because of compiler used, or compiler flag. I tend to just ignore them than fight with them. I use LSP only for auto completion.

Let me know if you want to query further

[FranckKernel]

Ok. Yeah, I got ccls working properly (or well, as good as vscode and arduino ide).

It seems in the video, ccls is being used. Yet some configuration change the auto completion menu style.

My clangd autocompletion menu is exactly like the one in the video. And my ccls completion menu is ever so slightly different. The same features are present.

One just done

ccls: f(args) -> output. | |comments
clangd: f(args) | | output, comments

Where there are two completion window.

---

If you have ccls working, and have an autocompletion style exactlt like the one in the video, you could send your config.

But at this point, it's a very minor and inimportant thing. It's more of an ocd, "Let's see if I can get it exactly that way for the sake of it" thing so... Don't waste too much time on my trifle.