I am on AstroNvim v5 and I only see 4 options when I press language server menu:
Nothing else. But my Neovim setup is fairly new so I might have botched it. I just don’t see searching through workspace symbols at all.
I know the mappings but they are literally not even present in my config.
Sorry, I am polluting the thread. This is my own Neovim probem. I’ll ping here when I figure it out.
Hello. I’m testing version 0.1.0-rc.5. It seems to work correctly with GNU Emacs 30.2 + eglot + eglot-booster. I think it can be already a LSP-server for everyday usage, at least for my purposes it works fine. Many thanks for your wonderful work!
Sometimes messages like the following appear:
[eglot] Server reports (type=1): [lib] Failed to start child {XPExpert.Project.Node, "lib"}: {:badrpc, {:EXIT, {{:badmatch, {:error, :erofs}}, [{XPForge.Project, :ensure_workspace_directory, 1, [file: ~c"lib/forge/project.ex", line: 241]}, {XPForge.Project, :ensure_workspace, 1, [file: ~c"lib/forge/project.ex", line: 224]}, {XPEngine.Bootstrap, :init, 5, []}]}}}
… I’m not sure what exactly they affect.
For me, code-actions are not working reliably from NVIM.
Would love to use refactorings: rename_function, extract_function, etc.
Anyone have success with this?
There is a tracking issue for refactoring here: Audit Refactorex features · Issue #265 · expert-lsp/expert · GitHub
Rename is not implemented in general. But extract_function should work, although perhaps not in a most friendly way. The comment says “Works, must select code independently valid as a function”, I’m not 100% sure what it means.
Can you describe in more detail what you tried?
Thanks - I didn’t realize there was an open issue for this. I’ll follow up on the tracker.
I see also, independent of ExpertLS, there is an NVIM plugin refactorex.nvim. I’ll have a look at that one also.
TIL
To use that code action in neovim, one needs to first visually select some code (and that selected code needs to be valid for a function body), then trigger vim.lsp.buf.code_action() (by default mapped to gra), then choose “Extract Function” from the list of code actions. If the selected code is not valid as a function body then “Extract Function” will not appear in the list of code actions after triggering vim.lsp.buf.code_action().
I am using the some of the code actions that Expert pulled in from RefactorEx (without using a separate plugin). As mentioned in my last comment, a lot of them require knowing what one needs to do before requesting available code actions.