Hi everyone!
The first release candidate for the Expert language server project is now available!
We’ve published a press release detailing all the work that has gone into it since ElixirConf 2025 on the website: The First Release Candidate | Expert
Thank you 
So grateful and excited! I’ve been using the nightly as my main driver for a while and its been working well 
Been waiting a long time for this. Starting to use it next week. Let’s see how much better it is!
I am using it for about a month already, and I loved it even before the RCs.
Find references works much quicker, it reports progress durings scanning, and formatting works instantly.
Very excited to see this as well! Glad to see the unified LSP finally has a release candidate.
Thanks to all of you for your efforts!
Woohooo, gonna try it today
wohoo 
, been on nightly for a while now. Finally time to move on to a proper release.
Thanks to everyone for their combined efforts !!
Congratulations and thanks to you and the team for all your hard work!
I’ve been using expert nightly builds since the initial open releases, and look forward to something even more stable.
Just installed it, works without a glitch!
Thanks @mhanberg
I tried it with vscode but after about 20 minutes the syntax checking starts telling me valid functions having missing end’s. And then my computer runs out of memory and grinds to a halt. It seems ok in zed though. So I guess I’m switching to zed for now.
Please open an issue
Cheers! This is exciting!
A few weeks ago, I tried Expert on a whim pre-rc and stumbled into a memory leak that eventually forced a VM restart. I didn’t have time then to investigate, but I’ll open/comment on an issue if it happens again.
I tried ExpertLSP with Neovim. At first glance: looking good!
GOTO-DEFINITION from heex component to source seems to work!! Also working: doc-hover for heex components!!!
The workspace_symbols page shows an example of telescope.nvim to fuzzy-find workspace symbols. Can anyone share their Nvim/Telescope config for this?
Yay!! Thank you all for your hard work work. Can’t wait to try it out.
Adding to the dogpile, I’ve been looking forward to this, too. Just updated my zed settings, and it went without a hitch.
Looks like that example is using Telescope’s lsp_dynamic_workplace_symbols picker, so this should do the trick:
vim.keymap.set("n", "<leader>ls", function() telescope.lsp_dynamic_workplace_symbols({ symbol_width = 60 }) end, opts)
I use lsp_document_symbols in my config, and it seems that lsp_dynamic_workplace_symbols doesn’t work on neovim 0.11 I got the same error reported here: Telescope LSP issues after update to Neovim v.0.11 · Issue #3438 · nvim-telescope/telescope.nvim · GitHub
Document symbols works fine though.
Edit: This is my current LSP setup. I program in several languages so there’s a bunch of other junk in here: dotfiles/.config/nvim/after/plugin/lsp.lua at main · GrammAcc/dotfiles · GitHub It’s pretty messy cause I was tweaking it to try out different LSPs when I last pushed my dotfiles.
Thanks for this! Very helpful. Here’s the abbreviated WhichKey config I used…
{"<leader>fD", "<cmd>Telescope lsp_document_symbols<cr>", desc = "Doc Syms"},
{"<leader>fW", "<cmd>Telescope lsp_workplace_symbols<cr>", desc = "Wrk Syms"},
Been using Expert on and off for a week – zero complaints or errors, love it.
I’d love to have workspace symbols integrated with snacks.nvim at one point, though that’s not on Expert’s team to solve.
Code actions would be next on my wishlist whenever time allows.
Can you clarify? I don’t think there is anything we need to do before you can use it with snacks, but I haven’t looked at snacks in a while so maybe I’m missing something.
Also in general please open issues for features you want, I’m only monitoring this thread and don’t look at the forum with any regularity.
© Copyright Elixir Forum | Terms | Privacy & Cookies
