-
Notifications
You must be signed in to change notification settings - Fork 2
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
Can't use plugins where binaries are used from PATH #32
Comments
I guess this is a sandbox issue again. You can try something like |
I'm having the same issue: I want to use the C# (omnisharp) plugin. It needs dotnet and omnisharp installed. I just downloaded omnisharp, put it in my home folder and specified its path in the plugin settings. For dotnet there is an extension (https://github.com/flathub/org.freedesktop.Sdk.Extension.dotnet7). The VS Code Flatpak uses a startup script to enable sdk extensions (https://github.com/flathub/com.visualstudio.code/blob/master/code.sh). Maybe Lapce could add something similar? The html lsp extension needs vscode-langservers-extracted, which I can install on my system using npm and access from the flatpak at |
I managed to get vscode-html-language-server and therefore the html lsp extension to work: Install node and vscode-langservers-extracted on host.
In the lapce settings for the html plugin set the path to html-language-server to
It shouldn't cause any major problems, as flatpak native binaries are preferred, because they are first in path.
Using I wouldn't recommend this, as it's pretty hacky and could easily break stuff. But at least it shouldn't break anything permanently and is easy to revert by just removing the environment variable overrides from the flatpak again. Ideally, lapce extensions should include or automatically download all required files and things like dotnet or node could be installed as flatpak extensions, like I described above. |
Maybe at least the PATH change could be done inside the flatpak permanently? Because then any LSPs that are self-contained (and don't rely on external libraries) would already work. |
There are some plugins which use the binary from system PATH.
Any idea how I can use those plugins with the Flatpak?
Works with the released binaries
The text was updated successfully, but these errors were encountered: