It is not possible to **not** use the bundled server
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 215
- Forks
- 62
- PR merge metrics
- No merged PRs in 30d
Description
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
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the VS Code plugin's server launch and bundled-binary configuration described in the issue. Add a setting that accepts an absolute path, relative path, or PATH-resolved command for the Lua language server, then verify that the configured executable is launched instead of the bundled binary, including on NixOS.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- lua, typescript
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 65/100