ccls icon indicating copy to clipboard operation
ccls copied to clipboard

C/C++/ObjC language server supporting cross references, hierarchies, completion and semantic highlighting

Results 169 ccls issues
Sort by recently updated
recently updated
newest added

#1 /home/funning/workspace/workspace/cclsTest/3dpatry/ccls/src/test.cc:66: warning: implicit conversion changes signedness: 'size_t' (aka 'unsigned long') to '__gnu_cxx::__normal_iterator::difference_type' (aka 'long') #2 /home/funning/workspace/workspace/cclsTest/3dpatry/ccls/src/test.cc:67: warning: implicit conversion changes signedness: 'size_t' (aka 'unsigned long') to '__gnu_cxx::__normal_iterator::difference_type' (aka 'long')...

Here are some things you should try before filing a bug report: + For client issues related to [emacs-ccls](https://github.com/MaskRay/emacs-ccls) or [vscode-ccls](https://github.com/MaskRay/vscode-ccls), report in their own repository. + For build problems,...

![图片](https://user-images.githubusercontent.com/7643216/145675556-463c5f56-fc8a-4aa5-b1aa-1e390b73624b.png)

Hi, my editor is vis and the lsp implementation that is available doesn't support workspaces. It currently works with clangd but I'd like to use ccls. How much work would...

I’d like to get ccls working with the WebKit browser sources from https://github.com/WebKit/WebKit. I have a .ccls file set up but not yet adequately for handling the idiosyncrasies of the...

Hi! Is it possible to correctly setup project for `ccls` when 2 or more different toolchains are used simultaneously? For example using local clang toolchain along with Android NDK toolchain....

### Observed behavior I set the "ccls.codeLens.enabled": true. There is a xxx refs above function, and I should clik the ref eveytime. ### Expected behavior I wish I could have...

I'm struggling to get ccls working with CUDA source files in my project. If I use the `compile_commands.json` file generated by cmake, ccls seems to fail to index the CUDA...

### Observed behavior A progress token is created only once (`window/workDoneProgress/create`) and over time gets re-used after `end` messages, but the LSP specification states: > #### [Server Initiated Progress](https://microsoft.github.io/language-server-protocol/specifications/specification-3-16/#serverInitiatedProgress) >...

Sadly there is some confusion about ranges in the LSP protocol. It turns out that VS code, when requesting code actions, sends range s,e in the request, with the associated...