vscodium: code-settings-sync extension cannot install extensions when using linux build
code-settings-sync extension cannot install extensions when using linux build. Tested on latest Ubuntu.
Steps to reproduce:
- Install latest linux build(either
amd64orx64) - Try to sync extensions using latest
code-settings-syncextension - Extension installation fails with following error
"bin/code" --install-extension stevencl.addDocComments
Error: Command failed: "bin/code" --install-extension stevencl.addDocComments
/bin/sh: 1: bin/code: not found
Reason:
- MacOS and Windows(probably) have
bin/codefile inside installation path, whereas linux builds havebin/vscodiumfile code-settings-syncextension resolvesbin/codebinary inside installation folder(source)
Why does it resolves to bin/code? Looks like issue with this line.
Eg: When debian build of VSCodium is installed, the vscodium binary path is resolved to /usr/share/vscodium/vscodium(initial myExt in above source) and then it resets it to bin/code.
I see that VSCodium support was merged to code-settings-sync here, this works fine. but this PR doesn’t cover linux path resolution fix while installing extensions.
Does this issue belongs here or should I raise the issue in code-settings-sync repo?
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Comments: 15 (5 by maintainers)
Hi @ganapativs! Thank you for this really well documented issue, that is very helpful. You might have already said this and I missed it, but does this extension work when using MS VS Code on Linux? Wondering if the extension just doesn’t know how to handle the Linux installation of VS Code or if it has to do with something we changed during build.
@ganapativs better move this issue to
code-settings-syncrepo.I tried to make the
bin/codesymlink, but it doesn’t fix the issue for Fedora 29.