You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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.
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
The text was updated successfully, but these errors were encountered: