dotfiles VS nvim-code-action-menu

nuxshed's dotfiles - of the JavaCafe01 vein, in particular pursuing the knockoff Neumorphic codepen look (that isn't actually Neumorphism as no object has a 3D appearance...) but this dev's code is relatively easy to parse the tea leaves of and if you dial back the Git history, you should be able to deduce something about implementing Rubato.

This is the way I have set it up as well, mostly because I made them before i was using LuaSnip and I'm too lazy to convert them all to lua.

hover, rename, code actions are all built into neovim. I liked lspsaga's rename popup, so i tried to recreate it from scratch. For code actions. im using telescope.

I believe this is the plugin, as i also use it

Is there a way to expose the extra commands therein through the native LSP code action experience or with an alternative code action UI like code-action-menu?

https://github.com/weilbith/nvim-code-action-menu looks cool, but it does far too much... diffs?!

there's a bug in nvim-lightbulb (I've commonly seen problems with using ipairs on the list of LSP clients)

I recently switched from Telescope for code actions to NeoVim Code Action Menu and I recommend it. I especially appreciate the built-in diff.

some plugins you might wanna look into: https://github.com/RishabhRD/nvim-lsputils https://github.com/weilbith/nvim-code-action-menu

I like to recommend my new plugin nvim-code-action-menu. I actually have this already for several months and use it every day. But I was always too busy (or rather too lazy) to wrap it up and write some docs etc. Anyway I decided to just "release" it now with the disclaimer of being beta and missing some docs. Though it should work quite well without effort out of the box. I would be happy to get feedback from you how well it works with other language servers. I strongly sticked to the Language Server Protocol specification and have good experience with the rust analyzer, tsserver and pylsp. The probably most useful feature is the diff preview for actions with a (workspace) edit. But it is also the part of the plugin I'm the least proud of the code. So if other plugin developers want to help here and improve it, I'm glad to receive pull requests and review them.