Closed CodePurble closed 3 years ago
Seems like nvim-lsp
is overriding coc.nvim
from the logs. I can also confirm that the experience is similar with nvim v0.4.4
, so I'm not sure whether nvim-lsp
is the culprit.
It's a coc.vim / coc-clangd problem. clangd/coc-clangd#287
I see. I guess I'll have to roll back my coc.nvim for now. Have you found any other workaround?
Since this is a problem with coc-clangd, I'm closing this issue.
Description Semantic highlighting with
coc-clangd
is not working. The defaultnvim
syntax highlighting seems to be taking over. No symbols are detected by the plugin for highlighting.To Reproduce
coc.nvim
coc-clangd
clangd
from standard repossudo pacman -S clang
which clangd
returns/usr/bin/clangd
, which is in myPATH
compile_commands.json
and open a source fileExpected behavior Semantic highlighting for
struct
s and classesScreenshots
:LspCxxHlCursorSym
output::LspCxxHlDumpSyms
output:Configuration
nvim --version
outputcoc-clangd v0.11.0
Log File:
Additional context I was previously using the stock builtin LSP for
nvim v0.5.0
. I then switched tococ-clangd
. I have used this before, and it had worked. I've also attached thecoc.nvim
logs for reference.