I’ve tried this and it doesn’t work. ElixirLS is still failing with the same error message.
satoru
satoru
Thanks.
This seems to be relevant to the issue.
After change projectDir to ".", ElixirLS works for all both existing and newly created mix projects. But it still fails when editing single files outside any project, eg, code hello.exs.
1
Dusty
Does it make any difference if you are inside a VS Code workspace or not? There are a few scenarios I can think of:
- You open a single file without opening any folder or workspace in VSC.
- You open a folder, but not a workspace, and:
a. The folder contains the file of interest.
b. The folder does not contain the file of interest. - You open a VSC workspace and:
a. The workspace contains the file of interest.
b. The workspace does not contain the file of interest.
I suspect your troubles may be related to the idea of spawning language servers per workspace. That might affect the scenario where you open a file outside any workspace, or where the file is not in the folder of the current workspace.
Perhaps one of the primary contributors can comment.
1
lukaszsamson
ElixirLS Core Team
After some testing I can tell that setting projectDir to "." doesn’t work as intended. It does though when set to "" (despite the validation error).
I’m afraid it’s not fully supported. Doing so currently results in an error
[Error - 9:05:45 AM] No mixfile found in project. To use a subdirectory, set `elixirLS.projectDir` in your settings. Looked for mixfile at "/Users/my_user/elixir_ls_test/mix.exs"
but the completions are still working (at least when running on development version of the extension). As a workaround you can open a mix project and then in the same workspace open the single file from the outside.
0