Skip to content
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

It is not possible to **not** use the bundled server #124

Open
NobbZ opened this issue Aug 10, 2023 · 3 comments
Open

It is not possible to **not** use the bundled server #124

NobbZ opened this issue Aug 10, 2023 · 3 comments
Labels
question Further information is requested

Comments

@NobbZ
Copy link

NobbZ commented Aug 10, 2023

Which OS are you using?

Linux

Expected Behaviour

I can specify and run an arbitrary location for the LSP binary.

Actual Behaviour

Only the bundled with the addon binary is used

Reproduction steps

Use this VScode plugin

Additional Notes

On NixOS binaries dowloaded from the web usually do not work, as their interpreter is not at the usual location that usually is assumed.

A common workaround we usually use is to use a softlink that replaces the binary to something we built with nix or set another location in VScode (we actually prefer the latter).

In a perfect world, the option can be either absolute, relative or just the binary for a lookup in the PATH.

(PS: the first version does also not work for this plugin, as then it follows the symlink and tries to write into a read only location, so I had to hardcopy the proper binary)

Log

[Error - 8:10:44 AM] Lua client: couldn't create connection to server.
Launching server using command /home/nobbz/.vscode/extensions/sumneko.lua-3.6.26-linux-x64/server/bin/lua-language-server failed. Error: spawn /home/nobbz/.vscode/extensions/sumneko.lua-3.6.26-linux-x64/server/bin/lua-language-server ENOENT
@sumneko
Copy link
Collaborator

sumneko commented Aug 10, 2023

Try setting: Lua.misc.executablePath

@sumneko sumneko added the question Further information is requested label Aug 10, 2023
@NobbZ
Copy link
Author

NobbZ commented Aug 10, 2023

That option seems to work when using an absolut path to the executable, it does not seem to be able to resolve from PATH.

@sumneko
Copy link
Collaborator

sumneko commented Aug 15, 2023

I think since this platform "disrupts" my file structure, the responsibility for compatibility should be on it. However, I don't mind if someone submits a pull request to improve compatibility on my end.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants