lspactions
nvim-code-action-menu
| lspactions | nvim-code-action-menu | |
|---|---|---|
| 2 | 8 | |
| 55 | 591 | |
| - | - | |
| 1.8 | 0.0 | |
| almost 2 years ago | 5 months ago | |
| Lua | Lua | |
| - | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
lspactions
-
How to config nvim-lspconfig to rename a variable?
The one I was using has a better UX, IMOO: https://github.com/RishabhRD/lspactions but the drawback of it is that it has too many dependencies.
-
Lspsaga alternative
I do a hobby project that is WIP but may interest you: https://github.com/RishabhRD/lspactions
nvim-code-action-menu
-
what neovim configuration is this?
I believe this is the plugin, as i also use it
-
Is there anyway to expose the undocumented TSServer commands to native LSP code action menu?
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?
-
Can I use nvim-cmp to select code actions?
https://github.com/weilbith/nvim-code-action-menu looks cool, but it does far too much... diffs?!
-
nvim-lspconfig error 'method textDocument/codeAction is not supported'
there's a bug in nvim-lightbulb (I've commonly seen problems with using ipairs on the list of LSP clients)
-
Lspsaga alternative
I recently switched from Telescope for code actions to NeoVim Code Action Menu and I recommend it. I especially appreciate the built-in diff.
-
lsp-saga alternatives
some plugins you might wanna look into: https://github.com/RishabhRD/nvim-lsputils https://github.com/weilbith/nvim-code-action-menu
-
Pop-up menu for code actions to show meta-information and diff preview
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.
What are some alternatives?
lsp-status.nvim - Utility functions for getting diagnostic status and progress messages from LSP servers, for use in the Neovim statusline
nvim-lsputils - Better defaults for nvim-lsp actions
CosmicNvim - CosmicNvim is a lightweight and opinionated Neovim config for web development, specifically designed to provide a 💫 COSMIC programming experience! [Moved to: https://github.com/CosmicNvim/CosmicNvim]
nv-ide - Neovim custom configuration, oriented for full stack developers (Ruby on Rails, ruby, php, html, css, SCSS, javascript)
nvim-config - :moon: Neovim configuration written primarily in lua
popfix - Neovim lua API for highly extensible popup window
web-tools.nvim - Neovim plugin for web developers
LunarVim - A Neovim config made with sane defaults
goto-preview - A small Neovim plugin for previewing definitions using floating windows.
navigator.lua - Code analysis & navigation plugin for Neovim. Navigate codes like a breeze🎐 Exploring LSP and 🌲Treesitter symbols a piece of 🍰 Take control like a boss 🦍
renamer.nvim - VS Code-like renaming UI for Neovim, writen in Lua.
plenary.nvim - plenary: full; complete; entire; absolute; unqualified. All the lua functions I don't want to write twice.