Skip to content

Commit fd1ab83

Browse files
authored
Document troublehsooting step for non-full erlang install (#219)
Fixes #208
1 parent e6f233a commit fd1ab83

File tree

1 file changed

+9
-0
lines changed

1 file changed

+9
-0
lines changed

README.md

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -118,6 +118,15 @@ Basic troubleshooting steps:
118118

119119
If your code doesn't compile in ElixirLS, it may be because ElixirLS compiles code with `MIX_ENV=test` (by default). So if you are missing some configuration in the test environment, your code may not compile.
120120

121+
If you get an error like the following immediately on startup:
122+
123+
```
124+
[Warn - 1:56:04 PM] ** (exit) exited in: GenServer.call(ElixirLS.LanguageServer.JsonRpc, {:packet, %{...snip...}}, 5000)
125+
** (EXIT) no process: the process is not alive or there's no process currently associated with the given name, possibly because its application isn't started
126+
```
127+
128+
and you installed Elixir and Erlang from the Erlang Solutions repository, you may not have a full installation of erlang. This can be solved with `sudo apt-get install esl-erlang`. Originally reported in [#208](https://github.com/elixir-lsp/elixir-ls/issues/208).
129+
121130
## Known Issues
122131

123132
* `.exs` files don't return compilation errors

0 commit comments

Comments
 (0)