Add LSP proxy to auto-switch clangd for subprojects #63
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
I'm making this PR just so I can have a record of this work. I think the idea is sound, but this shouldn't be within a single repo. This is something that a vscode workspace should use but not a specific repo within the workspace.
With the current clangd resolver, if you open the repo as the whole workspace, you get the clangd resolution. if you use this package within a greater workspace, then the hooks will not work. But in that case, you want something like this, so it bounces around depend on the files you are on. But that would be separate from anything libhal related.