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

Provide a way to restart cquery #39

Closed
Yanpas opened this issue Jun 20, 2018 · 5 comments
Closed

Provide a way to restart cquery #39

Yanpas opened this issue Jun 20, 2018 · 5 comments

Comments

@Yanpas
Copy link
Contributor

Yanpas commented Jun 20, 2018

Currently any change in compile_commands won't be relfected in cquery resulting that you need to reload vscode workspace. At the same time killing cquery process restarts cquery, but the restarted version is unusable since it generates a lot of warning if you edit the code.

@rocuh
Copy link

rocuh commented Aug 25, 2018

Just tried this hoping it would basically reload the compile_commands.json file and reindex. It didn't seem to do that, and I found syntax highlighting seemed to stop working properly after the restart command.

I found rather than doing

      languageClient.stop();
      languageClient = getLanguageClient();

doing this instead

languageClient.sendNotification('workspace/didChangeConfiguration');

got the what I would have expected of a restart.

@Yanpas
Copy link
Contributor Author

Yanpas commented Aug 25, 2018

I found syntax highlighting seemed to stop working properly after the restart command

I faced the same when I simply killed cquery process and the new spawned one didn't work properly

@rocuh
Copy link

rocuh commented Aug 25, 2018

sending the above notification definitely works it reloads the json and after it completed its jobs i got the correct inactive #ifdef'd regions for the build that generated the json which is what i was after.

@Yanpas
Copy link
Contributor Author

Yanpas commented Aug 31, 2018

I think this issue deserves separate ticket

@Yanpas
Copy link
Contributor Author

Yanpas commented Sep 16, 2018

@Roceh I've opened issue #50

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

2 participants