My apologies.
I think that you’re doing very interesting things, and the underlying idea (gen_lsp) is really interesting.
halostatue
3
dimitarvp
The way I read the motivation and the FAQ, it seems like the technical decisions you made are incompatible with ElixirLS’ architecture.
Fair enough, thanks for writing it down.
2
mhanberg
Expert LSP Core Team
The elixir-tools Update Vol. 4 has been released!
This is a fun release, because it introduces the beginnings of auto-completions!
7
mhanberg
Expert LSP Core Team
Several releases to share!
Next LS v0.15.0:
elixir-tools.vscode v0.12.0:
Tableau v0.8.0, v0.9.0, v0.10.0:
- Release v0.8.0 · elixir-tools/tableau · GitHub
- Release v0.9.0 · elixir-tools/tableau · GitHub
- Release v0.10.0 · elixir-tools/tableau · GitHub
Also the documentation website for elixir-tools has been revamped, and Next LS is the first to make its home there!
Check it out: Quickstart | elixir-tools
4
mhanberg
Expert LSP Core Team
@dimitarvp I believe Next LS has the two features you are wanting:
Symbols in the current file: Document Symbols | elixir-tools
Symbols in the space: Workspace Symbols | elixir-tools
3
dimitarvp
Thanks. I am open to try NextLS next.
Any omissions in the LSP protocol that could be important for day-to-day work?
In the case of Lexical, I was willing to overlook a bunch of things but definitely not the lack of listing symbols.
0
mhanberg
Expert LSP Core Team
mhanberg
Expert LSP Core Team
cjbottaro
Not sure if this is the right place to ask, but I’m using elixir-tools.vscode and now do end, fn->end don’t autocomplete anymore. Maybe autocomplete is the wrong word, maybe autoclose? I’m not sure what part of the toolchain is responsible for that, but ElixirLS did it and I miss it now! Thanks for the help/info.
0
mhanberg
Expert LSP Core Team
do doesn’t have a snippet attached to it, but with the latest version, if you enable autocomplete, there are snippets for most builtin functions like case and def and fn and those will expand and insert the end into the document.
1