Ensure clangd is executed in vscode.workspace.rootPath #153
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
If the rootPath of a project is a symlink vscode can execute clangd in the users home-directory. This can cause problems if one is, for example, using a wrapper script which relies on knowing the current project. This solves this issue by forcing the clangd to execute in `vscode.workspace.rootPath` if available. Test: manual
|
Just for background this is an issue I personally ran into since my job has a highly patched version of clangd in the path which breaks on some of the projects I work on. To work around this I have a script that looks at the current project and execs the appropriate clangd set as the global |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
If the rootPath of a project is a symlink vscode can execute clangd in
the users home-directory. This can cause problems if one is, for
example, using a wrapper script which relies on knowing the current
project. This solves this issue by forcing the clangd to execute in
vscode.workspace.rootPathif available.Test: manual