Seems like I don’t have to do anything extra, only restart my Emacs because it didn’t pick up the changes in ElixirLS upon reloading a buffer. But after that it did build the project with Erlang 24 / Elixir 1.12.
Thanks!
dimitarvp
dimitarvp
OK, here’s another question (or a request):
Can ElixirLS have several different releases compiled for different OTP versions and switch between them depending on which OTP version the project uses?
I have several projects that aren’t moving away to OTP 24 anytime soon and when I compile ElixirLS for it those projects’ LSP startup fails (I guess unsurprisingly). So I recompiled ElixirLS for OTP 23 but that will crash it when starting it inside OTP 24 projects.
After visiting an OTP 23 projects while ElixirLS is compiled for OTP 24 I get an error on the lane of “can’t find ElixirLS CLI module” or some such (can dig the error if you like).
axelson
Scenic Core Team
Version 0.8.0 was released today! 
Note that there are some deprecations in this release:
- Minimum version of Elixir is now 1.10
- Minimum version of Erlang/OTP is now 22
These are keeping in line with our Version Support Guidelines: elixir-ls/DEVELOPMENT.md at master · elixir-lsp/elixir-ls · GitHub
This release adds HEEx and Surface file support to ElixirLS, but for syntactical support VSCode users will want to wait for GitHub - phoenixframework/vscode-phoenix: Syntax highlighting support for Phoenix templates in Visual Studio Code. · GitHub which is still under development (ElixirLS itself doesn’t contain syntax support, that’s generally provided by an editor-specific extension).
Improvements:
- Watch HEEx and Surface files (thanks Marlus Saraiva) #583
- Basic single-file (e.g.
.exs) support (thanks Łukasz Samson) #562 (and VSCode #195) - Smarter spec suggestions in protocols and implementations (thanks Łukasz Samson) #549
- Trigger signature_help on comma (thanks Jared Mackey) #564
- ElixirSense: Add more fuzzy matching (thanks Maciej Szlosarczyk) #131
- ElixirSense: Add inference when using dependency injection with module attributes (Gustavo Aguiar) #133
- ElixirSense: Add support for EEP-48 (updated documentation storage format) (thanks Łukasz Samson) #132
Bug Fixes:
- Fix suggest contracts windows regression (thanks Łukasz Samson) #531
- Support exunit describe and test calls with unevaluated names (thanks Jonathan Arnett) #537
- Improve test runner to use exunit testPaths and testPattern (thanks Étienne Lévesque) #500
- Fix race-condition in suggest contracts (thanks Łukasz Samson) #544
- Fix
@doc falseand@moduledoc falsefor folding ranges (thanks Jason Axelson) #580 - Guard against sending -1 line or column locations in LSP messages (thanks Oliver Marriott) #558
- Handle Nova long form paths in rootURI (thanks Raul Chedrese) #579
Housekeeping:
- Minor iteration/performance improvements (thanks Andrew Summers) #527
VSCode:
- Support HEEx and Surface files (thanks Marlus Saraiva) #204
- Support optional
~Ssigil at start of doc folding region (thanks thepeoplesbourgeois) #179 - Fix run test command to save document before running tests (thanks Étienne Lévesque) #165
Note: There is beta support for a pipe/unpipe command (which I am very excited about), but it is not fully exposed in vscode-elixir-ls
As always, I want to give a huge thanks to all the contributors to this release!
32
axelson
Scenic Core Team
I believe it could, but someone would have to put in the work to make that work (and there was an emacs extension that supported that previously, although it was not automatic). Here’s the main packaging issue for reference: Discussion: Change packaging approach · Issue #115 · elixir-lsp/elixir-ls · GitHub
crispinb
Thanks to you & the other contributors for all your work. It makes the experience of learning & using Elixir far more pleasant than it would otherwise be. I for one am appreciative and hope to be able to give back in kind at some point 
cpgo
I’m just guessing here, but could be a refactor command to remove pipes or create pipes from function calls.
stefanluptak
Hi there. 
For elixir-ls to work in VSCode and Elixir 1.13 should I wait for a new release of elixir-ls or should it be already working? I am getting (CaseClauseError) at (elixir_sense 2.0.0) lib/elixir_sense/core/normalized/tokenizer.ex:16
axelson
Scenic Core Team
Yes a new release is necessary. I plan to cut one later today: