Closed Richie-Z closed 1 month ago
Does this PR follow the [Contribution Guidelines](development guidelines)? Following is a partial checklist:
Proper conventional commit scoping:
If you are adding a new plugin, the scope would be the name of the category it is being added into. ex. feat(utility): added noice.nvim plugin
If you are modifying a pre-existing plugin or pack, the scope would be the name of the plugin folder. ex. fix(noice-nvim): fix LSP handler error
[ ] Pull request title has the appropriate conventional commit type and scope where the scope is the name of the pre-existing directory in the project as described above
[ ] README
is properly formatted and uses fenced in links with <url>
unless they are inside a [title](url)
[ ] Proper usage of opts
table rather than setting things up with the config
function.
That's not the case with just the noice plugin. It must be a another plugin that causes that issue. Tested in base template + astrocommunity with noice.
📑 Description
when first opening neovim v0.10.0 with noice plugin installed it will throws error like this
vim.lsp.handlers["textDocument/signatureHelp"] has been overwritten by another plugin?
add
lsp = { signature = { enabled = false } }
to disabled the overwritten lsp signatureℹ Additional Information