-
Notifications
You must be signed in to change notification settings - Fork 411
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
Inconsistent behavior with rust-analyzer #2106
Comments
I've noticed this as well. Another way to trigger this odd behaviour is to type something like My config is below: local cmp = require("cmp")
cmp.setup({
snippet = {
expand = function(args)
require("luasnip").lsp_expand(args.body)
end,
},
mapping = cmp.mapping.preset.insert({
["<cr>"] = cmp.mapping.confirm({
behavior = cmp.ConfirmBehavior.Replace,
select = true,
}),
},
})
In comparison, Python (Pyright) and Go (gopls) are unaffected. |
FWIW, updating |
I still got this issue even after updating rust-analyzer to the mentioned version above. Did you change anything after updating @hejops ? |
I did not, unfortunately. |
It's the analyzer problem, not cmp. rust-lang/rust-analyzer#18547 |
IMO, this bug is solved by IMO, current Could you update |
Oh, sorry. I guess I misunderstood. It looks like we need to fix rust-analyzer, so please wait. |
This issue is resolved by updating rust-analyzer to |
FAQ
Announcement
Minimal reproducible full config
Description
When using nvim-cmp with rust-analyzer, showed completions are different from the completions, that actually get inserted. This happens only with rust-analyzer, no other lsp that I used.
Steps to reproduce
Just use the completion with the provided config
Expected behavior
Normal completion
Actual behavior
Completion of seemingly unrelated items
Additional context
With my config:
Bug.mp4
With minimal config:
Bug_minimal.mp4
The text was updated successfully, but these errors were encountered: