You can build and run it successfully on Linux - that’s said the support is still work in progress.
https://github.com/zed-industries/zed/issues/7015
https://github.com/zed-industries/zed/blob/main/docs/src/developing_zed__building_zed_linux.md
Eiji
2
seeplusplus
The broken vim mode is really obnoxious. No ability to paste from registers whilst doing a global search and replace is the worst.
0
alexandre
I started using, but it cannot find my elixir installation, since it is a custom installation (not brew). Has anyone found how to point zed to the path where elixir is?
1
Eiji
As long as you set PATH environment variable properly it should not be a problem I guess. I have installed Elixir via asdf on Gentoo Linux and after running zed cargo run --release ~/example, putting some empty lines in any of file inside example project and saving changes the file is properly formatted. I have also proper syntax highlighting. Make sure that in your ~/.bashrc (or equivalent file on MacOS) you have line like . ~/.asdf/asdf.sh before any interactive shell check, for example:
# before non-interactive check
. ~/.asdf/asdf.sh
# Test for an interactive shell.
if [[ $- != *i* ]] ; then
# Shell is non-interactive. Be done now!
return
fi
0
alexandre
stefanluptak
So I am happily using Zed for Elixir development for almost a month now. The only thing that causes me a bit of a trouble is when I am running tests for an umbrella app. In the terminal, the paths that are printed are in the form of lib/app_name/module_name.ex:123 instead of apps/app_name/lib/app_name/module_name.ex:123
This makes the paths non-clickable, so I can’t easily get to a failing test for example.
Did somebody make this work, or is there an issue that aims to resolve it? I was not able to find anything.
0
lud
Not sure how it is handled but you can always add a custom formatter for the tests results ; as a workaround.
I’d like to try zed now but did you install ElixirLS or another language server?
0
stefanluptak
Thanks for the tip for custom tests results formatter.
I am using Lexical with this in my settings.json (⌘,):
"elixir": {
"lsp": {
"local": {
"path": "<full_path_to>/lexical/_build/dev/package/lexical/bin/start_lexical.sh",
"arguments": []
}
}
}
EDIT: I made a GitHub Issue with feature request
1
lud
