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.
type1fool
AndyL
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?
1
idlehands
Author of Testing Elixir
wallyfoo
Adding to the dogpile, I’ve been looking forward to this, too. Just updated my zed settings, and it went without a hitch.
0
GrammAcc
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.
1
AndyL
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"},
1
dimitarvp
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.
0
mhanberg
Expert LSP Core Team
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.
0
dimitarvp
Apologies, I didn’t mean to use the forum thread as an issue tracker, no.
As mentioned, snacks.nvim is really not on you but on the community IMO.
I’ll have to switch between ElixirLS and Expert a few times in my work projects to be able to file up issue about code actions but they are generally stuff like “unfold imports” or “import this or that module that we can infer only from the last part of the name”, things like that. But I’ll formulate them better and file them up properly later, if somebody does not beat me to it.
0
mhanberg
Expert LSP Core Team
For now can you clarify what you meant about snacks tho, I’m still not certain what currently prohibits snacks from searching workspace symbols or triggering code actions.
0