That’s a bug in the archive does library. I think it’s fixed with a rm -r _build, although you might have to remove some tmp directories from the individual applications. There’s a closed issue for it but I don’t have the link handy.
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.
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).
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 which is still under development (ElixirLS itself doesn’t contain syntax support, that’s generally provided by an editor-specific extension).
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
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
The biggest change is that Elixir 1.13 is now supported ! Thanks @lukaszsamson !
Also fetchDeps now defaults to false (both in ElixirLS and vscode-elixir-ls) since it is prone to race conditions, especially with Elixir 1.13’s semantic recompilation. Thanks @jonleighton !
And PathGlob has been integrated to speed up formatting and avoid a costly Path.wildcard that has to hit the file system.
Hi @axelson, thank you for this update. As ElixirLS now supports elixir 1.13 should its formatting capabilities include plugins used in formatter.exs? I’m using surface_formatter that introduced this kind of plugin since version 0.7.2 and html tags are formatted correctly between ~F sigils on mix format run manually but not “on save” in VS Code where ElixirLS extension is used (elixir code is formated fine though).
Hi, I haven’t had a chance to test with a formatter plugins and some additional work in ElixirLS might be needed to support them. Are you configuring the formatter plugin in the root .formatter.exs file or is it inside a subdirectory? There’s some issues with subdirectory .formatter.exs that I’m currently working on that didn’t make it into the latest release.
This release brings improved compatibility with OTP 24 and 25 and a lot of new features. The biggest improvements are in debugger, see details below. Other include new completions in bitstring and sigil, fixed handling of MIX_TARGET and links to hexdocs in haver
Improvements to debugger adapter:
A lot of new features around breakpoints: function breakpoints, conditional breakpoints, hit count and log points #656, #661, #671 (thanks Łukasz Samson)