jinzhongjia / lspui.nvim Goto Github PK

I created this plugin just because I needed a stable lsp plugin (didn't follow many specifications), now I want to refactor the logic of the entire code and add new features

Some real-world testing is required before merging

Here are the features I think need to be added：

• declaration 585dcbf - 669c77c
• definition(not peek definition) 585dcbf - 669c77c
• type definition 585dcbf - 669c77c
• implemention 585dcbf - 669c77c
• reference 585dcbf - 669c77c
• code lens (Just server support is not enough)
• inlay hint #22
• callHierarchy #30
• add dynamic width to secondary

If you can see this issue, you can discuss what features need to be added！！

Features that have been refactored:

• rename eb3f31e
• lighthulb 949c80d - ad82527
• code_action ec0367b - 58f59ce
• diagnostic 9915ca2 - 27538e8
• hover 9c64a92 - 90a02dc

note:

The following are all completed

code action should provide registration method, for lua's code action
diagnostic should provide a diagnostic overview of the current workspace and files

Problems:

the keymap only will remove, we should restore keymap

Delete your repo. thief. You stole all glepnirr's code and ideas. You have not made any contribution or sponsorship to his project.
Obviously you are Chinese. Only you Chinese are so disrespectful of the spirit of open source. fucking stupid guy!! get fuck out of neovim

• vim.api.nvim_get_option replace use nvim_get_option_value
• vim.lsp.get_active_clients replace use get_clients
• vim.lsp.util.trim_empty_lines replace use vim.split (At present, it seems that it is not possible to achieve the effect of only clearing the first and last blank lines through vim split.)

This issue list some feature should be added or enhanced.

• CallHierarchy (But I don't know what the UI should be)
• code_action preview (waht the UI should be)
• rename preview (what the UI should be)
• new_hover (now, neovim's builtin hover highlight is not stable, when it is stable, I will switch the new highligtht)
• More efficient jump-history implementation (now is using tagstack)
• keybinding store and restore

Regarding design principles, you can read here, #12

Codeactions show a numbered list beside each action, and in other plugins (and even by default if I remember correctly) you can jump to and/or select an item by pressing that number, but as far as I can tell, pressing numbers has no effect when using this plugin.

Hi! first of all - thanks for creating this plugin. I arrived at it exactly for the same problem - every time I need to setup my nvim environment, lsp saga is broken for different reasons, I just cant afford wasting time on that over and over. Looking forward to try LspUI.

I am not an advanced nvim+lua user, I coudln't figure out how to bind commands from your docs. Could you give me an example, lets say how to bind code_actions command to <leader>ca?

Thank you!

Failed to run config for LspUI.nvim

...cal/share/nvim/lazy/LspUI.nvim/lua/LspUI/rename/util.lua:2: attempt to index field 'Methods' (a nil value).

How to fix it? Thank you!