Introducing ElixirLS, the Elixir Language Server

I have been using it with nvim-lsp package which’s provide language server setup including ElixirLS.

Version 0.6.0 was released today! :confetti_ball:

Here are the highlights:

General:

Major changes:

Improvements:

Bug Fixes:

  • Fix issue with formatting and deps handling (thanks Thanabodee Charoenpiriyakij) #345
    • This would manifest as ** (Mix.Error) Unknown dependency :ecto_sql given to :import_deps in the formatter configuration.
  • Fix formatting files in umbrella projects (thanks Drew Olson)#350
  • Fix callback suggesions (thanks Łukasz Samson) #359

Note: MIX_TARGET support was added in 0.5.0 but wasn’t added to the changelog until later:

  • Support MIX_TARGET so the language server can have target specific contexts, like with Nerves (thanks Jon Carstens) #299

Potentially breaking changes:

  • Do not format files that are not listed in inputs of .formatter.exs (thanks Tan Jay Jun) #315
    • Note this is especially important for files like mix.lock
  • Drop OTP 20 and Elixir 1.7.x support and set some version support guidelines (thanks Jason Axelson) #337

I want to give a huge thanks to all the contributors to this release! :heart:

Full Changelog

30 Likes

This is an awesome release :heart_eyes: Kudos to all who contributed!

I’ve just upgraded but the extension seems to have issues loading.

I’ve opened an issue here https://github.com/elixir-lsp/elixir-ls/issues/371 and will try to address later when time permits.


Update: seems to be a VS Code package issue so moved it to the right repo https://github.com/elixir-lsp/vscode-elixir-ls/issues/145

3 Likes

Yeah, turns out there were a couple issues with the packaging for the VSCode extension for 0.6.0. I’ve released a new version of the VSCode extension (0.6.1) that resolves them.

2 Likes

Apologies if I am just barging in to ask – what is the status of an Emacs LSP-mode integrated server? I am looking for something like in Rust where you can automatically call format on save, jump to definitions, run various mix sub-commands.

Last few updates I’ve seen:

Is there anything newer? Is there an officially blessed way to run ElixirLS with Emacs?

ElixirLS can do all of those except running arbitrary mix commands.

There’s two main LSP packages to use with Emacs, lsp-mode and eglot. lsp-mode is more featureful and what I would generally recommend (and is what I personally use). This wiki is generally up to date and a good overview: Emacs - Elixir Setup Configuration Wiki

4 Likes

Took me some fighting until I pinpoint where and what to put in ~/.spacemacs but it looks like it’s working now. Thank you for the pointer!

Is there an option to run mix format on a file after save?

Yes:

2 Likes

Thanks. I’m using Spacemacs casually for several months and still haven’t learned to properly customize it. Any idea where exactly in its init file should I put this block?

You do not need the full block, I just posted the full area because it was simpler for me :smiley: And sadly I can not tell where to put that in spacemacs.

Its basically the reason why I dropped spacemacs. All packages READMEs assumed vanilla emacs + use-package. It usually took me hours to find out where to put stuff.

After I dropped spacemacs and did a free form emacs config, which I later split into many files, organized similar to how Steve Purcell did, it became a lot easier. Eventually I got to the point where I had everything I need in my emacs config, and even though I did not leverage lazy loading, the config loaded within 5 to 7 seconds, while spacemacs never really got below 20, despite the fact that it advertised itself as “fast”.

Also, perhaps its time that someone opens an issue at spacemacs and tells them that Alchemist is not state of the art anymore but anyone uses lsp-mode/eglot + the LS.

PS: The important part is actually this:

(add-hook 'elixir-mode-hook ;; when we enter elixir mode
          (lambda ()        ;; call this function
            ;; Format on save, this buffer only.
            (add-hook 'before-save-hook #'lsp-format-buffer nil t)))

If you use eglot rather than lsp-mode you need to figure out what function you have to put there in the hook.

3 Likes

Thank you. Only added that last block to Spacemacs’ dotspacemacs/user-config function so now it looks like this:

(defun dotspacemacs/user-config ()
  (use-package lsp-mode
    :commands lsp
    :ensure t
    :diminish lsp-mode
    :hook
    (elixir-mode . lsp)
    :init
    (add-to-list 'exec-path "/Users/dimi/bin/elixir-ls/release"))

  (add-hook 'elixir-mode-hook
            (lambda ()
              (add-hook 'before-save-hook #'lsp-format-buffer nil t)))
  )

lsp-mode plus elixir-ls work, and so does formatting on save.

Very grateful for the assist. :023:

1 Like

Version 0.6.2 was released today! :tada:

Here are the highlights.

Improvements:

  • Add setup.bat support for windows (thanks E14) #374
  • Add a message when done fetching deps #380

Changes:

  • Remove query prefixes from workspace symbol search (the functionality is now longer supported by VSCode) (thanks Łukasz Samson) #396

Bug Fixes:

  • Improve formatting speed (thanks Matt Baker) #390
  • Fix warnings and errors around starting wx (thanks Łukasz Samson) #388
    • This fixes an issue when running ElixirLS in VSCode remote dev containers
  • Fix formatting on windows (thanks Po Chen) #375

VSCode:

Also:

As always, I want to give a huge thanks to all the contributors to this release! :heart:

Full changelog

9 Likes

The patch is open on vim-lsp-settings https://github.com/mattn/vim-lsp-settings/pull/341. :slight_smile:

1 Like

Did a git pull the other day and then git checkout v0.6.2. Both Elixir and Rust language servers fail with reasons I can’t find. Where should I look?

With Elixir I get “Server <…> status:starting exited with status exit. Do you want to restart it?”-- even if I press Y the same things happens until I press N.

Can anyone help?

EDIT: Sorry, had a bad day. It was as simple as asdf local erlang 23.1.5 because my project used an older version that I’ve since deleted. Apologies for polluting the thread.

2 Likes

Version 0.6.3 was released today! :confetti_ball:

Here are the highlights:

Major changes:

Improvements:

Bug Fixes:

Housekeeping:

VSCode:

As always, I want to give a huge thanks to all the contributors to this release! :heart:

Full changelog

33 Likes

0.6.4 was released today which has a hotfix for a startup issue that was primarily affecting macOS:

7 Likes

0.6.5 was released to which has a hotfix for a regression introduced in 0.6.3:

This would often manifest when VSCode had staged or unstaged changes.

10 Likes

Version 0.7.0 was released today! :confetti_ball:

Here are the highlights:

Major Changes:

  • Support auto-generating folding ranges (textDocument/foldingRange) (thanks billylanchantin (inspired by an initial PR by Thanabodee Charoenpiriyakij) #492

    • Example: Screenshot 2021-03-29 08.15.31
    • For VSCode this will work automatically, other editors may need to enable LSP folding range support explicitly
  • Use fuzzy matching for function completion (thanks Po Chen) #491

    • For example: “valp” will match validate_password and “Enum.chub” will match Enum.chunk_by/2
    • Note: the plan is to extend this fuzzy matching to other types of completion in the future, please try it out and give us feedback!

Improvements:

Bug Fixes:

  • Make expandMacro a custom command (thanks Łukasz Samson) #498
    • Will need to be bound in your editor to make use of it
  • Suppress setup script stdout output on windows(thanks Po Chen) #497

Housekeeping:

  • Improved support for OTP 24 (thanks Tom Crossland) #504
    • Note that OTP 24 isn’t officially supported since it is not yet released

VSCode:

Deprecations
Deprecate non-standard elixirDocument/macroExpansion command. It is being replaced with the expandMacro custom command. See #498 for details. It is planned to be fully removed in 0.8

As always, I want to give a huge thanks to all the contributors to this release! :heart:

Full changelog

27 Likes

Hi Jason,

There is a minor error in the description about the fuzzy matching. valword will actually match validate_password. The first character restriction is only applied to the very first character of the whole function name. If the trigger word doesn’t start with v it would not match, like if one types dw wouldn’t get validate_password, but vpw, vp or vw will.

4 Likes

Thanks, updated!

1 Like