-
Notifications
You must be signed in to change notification settings - Fork 115
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
[feature request] Pause indexing #737
Comments
From a quick test, in linux just doing a sigstop (19) / sigcont(18) seems to do the work very well. |
Are you looking to pause the clangd server process altogether, or just the background indexer? Sigstop has the effect of the former, which means e.g. hover or go-to-definition in an open file will also not work during the pause. |
Indeed I would like to still work during compilation, so the first. I would
imagine that's a clangd request then. Although ,having the former one until
it is implemented on the server side wouldn't be a bad thing, as I can
still work using the search tools to find definitions and so on.
…On Fri, Nov 22, 2024, 23:06 Nathan Ridge ***@***.***> wrote:
Are you looking to pause the clangd server process altogether, or just the
background indexer? Sigstop has the effect of the former, which means e.g.
hover or go-to-definition in an open file will also not work during the
pause.
—
Reply to this email directly, view it on GitHub
<#737 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAC2CFXOILXV2UN75BTTG4T2B6THHAVCNFSM6AAAAABSJLXZQKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOJUHE2DKOBZGQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
I wish stop cpu & memory consuming if some build task (compilation) is running. |
Hi,
while performing huge changes (e.g. merging llvm-project from upstream that changes 3k files) frequently I get to compile while clangd is indexing the project it self. It would be most useful to be able to pause (or kill) / resume (or restart) clangd's indexing from vscode.
The text was updated successfully, but these errors were encountered: