Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Should the extension activate in presence of compile_commands.json or .ccls-cache ? #121

Open
kartikeyshetty opened this issue Jul 1, 2021 · 0 comments

Comments

@kartikeyshetty
Copy link

I have been using vscode-ccls in my project which is fairly large ( a few GBs ). I have a compile_commands.json setup in my project for CCLS to refer. This works fairly well.

My issue though is that the extension only activates when a C file is opened. Generally this would not be a problem, but if a compile_commands.json is already present, CCLS does not start indexing until a C file is opened. This behaviour extends to .ccls-cache, where the cache isn't loaded until i start working on a C file.

Ideally, to have CCLS start indexing on compile_commands.json/.ccls-cache detection would reduce overall wait time to the user.

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

No branches or pull requests

1 participant