Open AlphaKeks opened 1 year ago
+1 I'm experiencing this with ccls as well.
The suggested result for a variable often includes the type:
variable_name : type
And the suggested result for a function includes the return type:
function_name() -> return_type
I have a relatively minimal config:
local coq = require('coq')
require('lspconfig')['ccls'].setup(coq.lsp_ensure_capabilities({
init_options = {
cache = {
directory = "/tmp/ccls"
},
compilationDatabaseDirectory = "builddir",
client = {
snippetSupport = true
},
highlight = {
lsRanges = true
}
}
}))
require('lspconfig')['rust_analyzer'].setup(coq.lsp_ensure_capabilities({
}))
vim.g.coq_settings = {
clients = {
lsp = {
weight_adjust = 1.5
},
snippets = {
enabled = false
}
},
display = {
pum = {
-- Helps prevent flickering at the risk of having stale results.
fast_close = false
}
}
}
Sometimes when accepting suggestions it expands into the wrong thing. Let's say I have a
Vec
in rust and want to call.into_iter()
on it. When I start typing, the LSP correctly suggests it. Now when I accept the suggestion it does not expand it into.into_iter
(which would be what I expect) but into.into_iter (as IntoIterator)
.I'm using neovim 0.8 and this is my config:
I tested it with and without nvim-autopairs installed. It doesn't seem to have any effect on the behavior. A full list of my plugins: