Open camstuart opened 1 month ago
I noticed this as well @camstuart and by making all the "default" scripts executable (not only language_server.sh
) it started to work again for me (macOS 14.6, M1). By the default scripts I mean these:
debug_adapter.bat
debug_adapter.sh
exec.bash
exec.zsh
language_server.bat
language_server.sh
launch.sh
(I compared the elixir-ls release with what VSCode does with the plugin).
I noticed this as well @camstuart and by making all the "default" scripts executable (not only
language_server.sh
) it started to work again for me (macOS 14.6, M1). By the default scripts I mean these:debug_adapter.bat debug_adapter.sh exec.bash exec.zsh language_server.bat language_server.sh launch.sh
(I compared the elixir-ls release with what VSCode does with the plugin).
Fantastic, thanks @anderkonzen that did the trick
I have lexical installed myself, do you know the correct settings incantation to point to it @anderkonzen ?
The auto download feature is nice, but I do like having my own LSP. easier to manage versions and updates
launch.sh
That did the trick for me as well, thanks :)
I have lexical installed myself, do you know the correct settings incantation to point to it @anderkonzen ?
The auto download feature is nice, but I do like having my own LSP. easier to manage versions and updates
I'm not sure if this is supported yet... There seems to be some open issues regarding this here #4978, and I understood that zed is pushing LSP logic to the language extensions (https://github.com/zed-industries/zed/issues/7902#issuecomment-1956436123). Maybe the elixir extension needs to be updated to be smart about detecting LSPs.
I have lexical installed myself, do you know the correct settings incantation to point to it @anderkonzen ? The auto download feature is nice, but I do like having my own LSP. easier to manage versions and updates
I'm not sure if this is supported yet... There seems to be some open issues regarding this here #4978, and I understood that zed is pushing LSP logic to the language extensions (#7902 (comment)). Maybe the elixir extension needs to be updated to be smart about detecting LSPs.
The Elixir extension already does support using a language server already on the PATH:
elixir-ls
: https://github.com/zed-industries/zed/blob/7cef5b29566dac6d9319e67956136955db1b7535/extensions/elixir/src/language_servers/elixir_ls.rs#L26-L28lexical
: https://github.com/zed-industries/zed/blob/7cef5b29566dac6d9319e67956136955db1b7535/extensions/elixir/src/language_servers/lexical.rs#L45-L50next-ls
: https://github.com/zed-industries/zed/blob/7cef5b29566dac6d9319e67956136955db1b7535/extensions/elixir/src/language_servers/next_ls.rs#L25-L27
Check for existing issues
Describe the bug / provide steps to reproduce it
I have noticed noticed "Go to definition" has stopped working in my Elixir projects over the past few days. Both with command click, f12, right click "Go to definition"
At first I suspected the LSP. So I have tried with all 3 (lexical, elixir-ls, next-ls) and tried restarts (zed and my macbook) along with updates to Zed (now at version: 0.146.5 / 582ad04710e96ad7f6a443e9baf8362c882fda03)
Here is the current state of my settings:
The logs definitely show an issue with the language server. I tried running it on the CLI and discovered the shell script:
/Users/cam/Library/Application\ Support/Zed/extensions/work/elixir/elixir-ls-v0.23.0/language_server.sh
was not executableSo I chmod'd 755, and now see this error in. the logs:
Environment
Zed: v0.146.5 (Zed) OS: macOS 14.6.0 Memory: 64 GiB Architecture: aarch64
If applicable, add mockups / screenshots to help explain present your vision of the feature
No response
If applicable, attach your Zed.log file to this issue.
zed.log