-
-
Notifications
You must be signed in to change notification settings - Fork 34
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
Specifying clangd version or having a common path #523
Labels
enhancement
New feature or request
Comments
Hi, sorry for the very late reply, I'm new to this repo.
fixes it instantly, if you have internet access, I don't think it would be a hassle. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I like to sync my configuration files across different machines using git repository. One of the files, which is shared is
coc-settings.json
.If machine doesn't have clangd installed, then we can install using
CocInstall clangd.install
.This creates a folder in ~/.config/coc/extensions/... and adds it to field
clangd.path
coc-settings.json
.Issue:
If one executes clangd.install on different days on different machines, then they will have different versions of clangd installed (which is fine).
But, everytime I sync coc-settings.json, there will be a file conflict due to systems having different clangd versions installed.
v/s
Workaround:
One workaround will be for me to update each machine I have with clangd.install to make sure I have latest version. But that will require me to manually keep track of versions and updating the corresponding machines. This will be hard and I would like an automatic approach.
Expectation:
Is it possible to add a feature (if one doesn't exist) :
If anyone knows better way to synchronize coc-settings.json across different machines, I am open to suggestions.
Thanks
The text was updated successfully, but these errors were encountered: