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.
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.
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!
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.
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.
