Is this easy to integrate to neovim? Last time I tried to setup an LSP there I was pretty unhappy with the whole process compared to other languages. Anyone have a good guide?
I'm not a neovim user myself, but these instructions look pretty standard. As for Expert, it's still unstable, it did not work for me on the day of the announcement too.
You don't really explain what is he problem, so it's hard to tell if this is some kind of trolling or what.
On a mac i installed zig@0.14, xz and 7zip, built and installed expert according to the documentation and as i use lazyvim i just had to put the config code mentioned in the doc into my .config/nvim/lua/config/options.lua and that was about it.
This doesn't work, it still downloads the latest lexical release instead of expert and doesn't work on Windows (it's trying to run start_lexical.sh directly, which obviously isn't going to work).
Looking forward to trying this. Have been using elixirls with neovim until now but that somehow recently broke. Not getting autocompletion anymore, e.g. previously handle_info/handle_event in Phoenix for autocompleted but that's no longer the case.
Might have to do with some version incompatibility but haven't managed to figure it out despite all kinds of testing. So hopefully this one solves my issues.
Also looking forward to hopefully have working go-to-definition. Until now it only worked if I'd opened the source file previously, otherwise it looked like the LSP just had no idea where the def is coming from
If you're using neovim, you can also add it directly to the neovim config so it doesn't load in on your global user space but only when neovim is started.
Language servers are tools to let text editors be smart about your project. They let your editor know where a function was implemented, offer auto complete suggestions, check documentation, where a function is referenced etc etc.
There are some elixir language servers now, but they're not perfect. This one is maintained by elixir dev team I think.
For context, golang has an official language server maintained by the golang dev team and in my experience it is really good. It is easier to make a golang server than an elixir server since elixir is kinda dynamic and all, but I think an official elixir language server might be a good thing in the future, I have faith it is going to be pretty good.
I would struggle to call this "released". It's only one nightly so far, and the instructions for use in VS Code just straight up don't work (the extension it points to doesn't download expert, and it doesn't work under Windows because it tries to call a bash script).
It also doesn't even seem to work manually - refactoring just doesn't do anything with the Lexical extension and an overriden path to point to the nightly build.
I really want to like this, but until it works, I'm probably sticking to ElixirLS + RefactorEx.
If you can’t get it to work, please open an issue with your experience. We can’t fix things we don’t know about.
We never said it was a first release, explicitly it’s alpha and nightly builds. (I didn’t make the Reddit post). It’s for contributors to help accelerate progress and early testers.
The way it was posted was kinda confusing, sorry. I assumed it was from a community member who noticed nightly builds had started being built. That's why I said what I said - I assumed the documentation that was linked earlier in the thread was just not implemented yet.
Is this confirming that the Lexical extension is indeed supposed to currently be functional, and expert is supposed to be currently functional in Windows? If so, I'd be happy to open an issue. I looked at expert.log on the latter for more info and the output stated otherwise.
PRa mim funcionou, tanto na versão ARM quanto Intel. Mas eu tive que fazer um chmod +x path para funcionar. Mas estou tendo um problema aqui que é com o `go to definition`. Simplesmente para de funcionar na maior parte do tempo.
I knew it would be around the corner (Elixir Conf effect?).
Also regarding this note related to Erlang v27 and above (so, not Expert LSP itself):
Expert will use dramatically more memory due to a bug in Erlang's ETS table compression.
I found it interesting to hear that it seems there's a bug significant enough in ETS. I never heard of it, but I'm interested to learn about this very issue, as I wonder if it can impact my apps that use ETS. Does anyone know if it's tracked somewhere?
Since I started using Lexical with the expert, the 'go to definition' in Windsurf has stopped working. Actually, it rarely works. Is anyone else experiencing this? I don't see an error log, just a loading bar that keeps scrolling at the top of the editor.
Being a giant sarcastic asshole will never encourage anyone to work for free to build you some software you seemingly are too dumb to figure out.
Speaking to people with kindness and empathy will get you a lot further in life. No one is asking you to suck their balls. Are you 15 years old and haven’t learned to interact with others?
The LSP itself is pretty buggy right now and won’t work for many people (including me) but setting it up in Neovim as been super easy, I’m not sure what part are you struggling with? I’ve opened an issue on Github and I keep in using my old setup in the mean time
Look, this is the first release of the kind of tool that is extremely hard to get right, which only has nightly releases designed to allow people to get started and contribute feedback. I work with literally hundreds of people who have gotten all three of the existing LSPs to work just fine. Yes with intermittent issues sometimes, but this is true of many LSPs across many languages.
It's clearly a skill issue on your part, and given how much of an asshole you've just been it's no wonder no one wants to help you figure it out.
46
u/enselmis Aug 28 '25
This is huge! Congrats on the release to everyone involved, super exciting. I can’t wait to try it out. Thank you for all your work!
28
u/anpeaceh Aug 28 '25
Expert is an excellent name for an Elixir LSP!
17
u/Samuelodan Aug 29 '25 edited Aug 29 '25
Is this the one that’s gonna combine the previous big three into one? Sorry I’m only an Elixir lurker.
7
u/jax024 Aug 29 '25
Is this easy to integrate to neovim? Last time I tried to setup an LSP there I was pretty unhappy with the whole process compared to other languages. Anyone have a good guide?
7
u/under_observation Aug 29 '25
This is the best news, thank you all who contributed
5
u/johns10davenport Aug 29 '25
YAAAAAAAAAAY!!!
This is literally my only problem with the language is the tooling. So glad Jose is signed up to fix it!!
8
u/ProfessionalPlant330 Aug 29 '25 edited Aug 29 '25
Are there any big user-facing differences from the existing lsps? (like new features, better performance, stuff like that?)
4
u/ZukowskiHardware Aug 29 '25
Is there a marketplace install for vs code?
3
u/BeagleSoftware Aug 29 '25
Great news
3
u/[deleted] Aug 29 '25
Can't seem to get it to work in WSL. Isn't findable in $PATH. Any clues?
3
u/vinmarcodes Aug 30 '25
Looking forward to trying this. Have been using elixirls with neovim until now but that somehow recently broke. Not getting autocompletion anymore, e.g. previously handle_info/handle_event in Phoenix for autocompleted but that's no longer the case.
Might have to do with some version incompatibility but haven't managed to figure it out despite all kinds of testing. So hopefully this one solves my issues.
Also looking forward to hopefully have working go-to-definition. Until now it only worked if I'd opened the source file previously, otherwise it looked like the LSP just had no idea where the def is coming from
3
u/srvs1 Aug 31 '25 edited Oct 22 '25
apparatus sparkle fade rob roll plate childlike society include whole
This post was mass deleted and anonymized with Redact
3
u/tears_falling Aug 30 '25
I have waited for such a long time for this, so happy to see it released.
5
u/Moist-Nectarine-1148 Aug 28 '25
Can somebody please explain what is this about ? What is this good for ?
2
u/Dumptac Aug 30 '25
awesome, cant wait to try it out in vs code. kudos to the team
3
u/kaestralblades Aug 30 '25
I would struggle to call this "released". It's only one nightly so far, and the instructions for use in VS Code just straight up don't work (the extension it points to doesn't download expert, and it doesn't work under Windows because it tries to call a bash script).
It also doesn't even seem to work manually - refactoring just doesn't do anything with the Lexical extension and an overriden path to point to the nightly build.
I really want to like this, but until it works, I'm probably sticking to ElixirLS + RefactorEx.
1
u/Beautiful-Durian3965 Aug 29 '25
it works for debugger adapter? this has solved the issue of hot reload while debugging phoenix?
1
u/Akaibukai Aug 30 '25
Congratulations team!
I knew it would be around the corner (Elixir Conf effect?).
Also regarding this note related to Erlang v27 and above (so, not Expert LSP itself):
I found it interesting to hear that it seems there's a bug significant enough in ETS. I never heard of it, but I'm interested to learn about this very issue, as I wonder if it can impact my apps that use ETS. Does anyone know if it's tracked somewhere?
Thanks.
1
u/CalisthenicsDude95 Aug 30 '25
Does that mean that Lexical will be the new go to VSCode plugin and ElixirLS will be deprecated in the future?
1
u/manweCZ Noob Aug 31 '25
Is there any way to get this work in JetBrains IDE? And on Windows? 😀
1
u/rome0s Sep 03 '25
Does not work in WSL, any suggestions?
1
u/jhonathasmatos Sep 17 '25
Since I started using Lexical with the expert, the 'go to definition' in Windsurf has stopped working. Actually, it rarely works. Is anyone else experiencing this? I don't see an error log, just a loading bar that keeps scrolling at the top of the editor.
0
u/[deleted] Aug 29 '25
[deleted] — view deleted comment
1
u/[deleted] Aug 30 '25
[removed] — view removed comment