Skip to content
This repository has been archived by the owner on Feb 8, 2024. It is now read-only.

Cquery Support #173

Open
Piping opened this issue Aug 10, 2018 · 3 comments
Open

Cquery Support #173

Piping opened this issue Aug 10, 2018 · 3 comments

Comments

@Piping
Copy link

Piping commented Aug 10, 2018

Hi,

Is it possible to utilize the cquery language server (which uses the clang as well) to provide c++/c semantic highlighting?

Right now I have three copies of clang in my system..

@jeaye
Copy link
Owner

jeaye commented Aug 10, 2018

Hey there! This is something, in general, which has been discussed many times. I'd love for color_coded to not have its own copy of clang, and I'd really love to be able to use YouCompleteMe to get access to the AST. There's even a similar project to color_coded which does this, using its own fork of YCM.

Moving forward, coming up with a solution to this, whether it's YCM or not, will be a good move for color_coded. I'm not writing C++ much these days, so most of the development done is by the community (and a couple heroes in particular). Let's leave this discussion open and see what comes from it.

@UnrealQuester
Copy link
Collaborator

There is currently a proposal to standardize this in the language server protocol.

But I am not sure if implementing this (or just the cquery implementation) is in scope for this plugin as this would be pretty much a complete rewrite. Maybe this should be part of lsp client plugins for vim/nvim, as they already handle the management of the language servers.

@Piping
Copy link
Author

Piping commented Aug 10, 2018

@jeaye in my humble opinion, if color_coded can add an options for using cquery-clang (the clang compiled by cquery) that would be great already! YCM just seems too huge for me and I never get it working properly..

@UnrealQuester Yes, there is still a lot of debate whether the syntax highlighting should be part of language server protocol ( I believe it is ). However, the actual displayed is tightly coupled with editor itselves.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants