-
Notifications
You must be signed in to change notification settings - Fork 404
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"..." instead of completion #2086
Comments
I had encountered the same issue. After lots of trails and errors I've nailed down to vim.g.rustaceanvim = {
server = {
capabilities = {
textDocument = {
completion = {
completionItem = {
snippetSupport = false
}
}
}
}
}
} solves the issue for me. Digging the rabbit hole leads me to https://github.com/rust-lang/rust/blob/78bb5ee79e0261e8e47476b631da02acc1cb03ef/src/tools/rust-analyzer/crates/ide-completion/src/render/function.rs#L278 where the |
Thank you, it works, but now snippets, that may be interpreted like lsp completion For example |
OK after some git bisection I've found hrsh7th/cmp-nvim-lsp@44b16d1 to be the culprit. Overriding these properties one by one reveals A quick search then reveals hrsh7th/cmp-nvim-lsp#72 (which has a confusing and unrelated name for those unfamiliar with LSP internals like me...), and using codes from hrsh7th/cmp-nvim-lsp/72#issuecomment-2425963432 solves the issue while allowing snippet completion. We probably should close this issue as dupe and track the progress on hrsh7th/cmp-nvim-lsp#72? |
Issue related to another repo. |
FAQ
Announcement
Minimal reproducible full config
init.lua
Description
with rust:
Screencast.From.2024-11-07.09-33-42.mp4
with python for example(or other):
Screencast.From.2024-11-07.09-36-37.mp4
Steps to reproduce
Expected behavior
work as first completion(only brackets, cursor inside, no
...
)Actual behavior
...
inside brackets second brackets after and cursor in themAdditional context
In my config specified rustaceanvim version = "^4" from start.
This issue happens only few month, not from start 100%.
Issue occurs even on version "^3".
So I think issue in your plugin, not rustaceanvim.
The text was updated successfully, but these errors were encountered: