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

Prompt when workspace overrides clangd.path and clangd.arguments #160

Merged
merged 2 commits into from
Mar 2, 2021

Conversation

sam-mccall
Copy link
Member

No description provided.

@sam-mccall sam-mccall requested a review from hokein March 2, 2021 09:34
Copy link
Collaborator

@hokein hokein left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks, looks pretty solid. I also test it locally.

@hokein hokein merged commit 395bfe1 into master Mar 2, 2021
@hokein hokein deleted the secureconfig branch March 2, 2021 10:28
@adzenith
Copy link

adzenith commented Mar 8, 2021

Is there any way to reset this if you accidentally click "no" at the prompt?

@sam-mccall
Copy link
Member Author

We save the answer for the latest value seen of each setting. So you can change the setting in workspace/.vscode/settings.json and reload the window to get re-prompted. (And then, change it back!)

@simon8233
Copy link

simon8233 commented Mar 21, 2022

is it any way to disable it?
like $HOME/.clangd_config
we use clangd.path and clangd.arguments and remote index server setup as one workspace file in internal.

any suggestion or help for me.
I very appreciate

@simon8233
Copy link

sorry for ask this question again.
is it possible to add configure option in clangd configure of User level VS Code or $HOME/.clangd

i not sure is it ok solution for clangd development roadmap.

@HighCommander4
Copy link
Contributor

@simon8233 it might be easier for the question to be noticed if you file a new issue for it

@simon8233
Copy link

Thanks for your feedback. I will raise question for this.

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

Successfully merging this pull request may close these issues.

5 participants