-
Notifications
You must be signed in to change notification settings - Fork 17.7k
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
x/tools/gopls: v0.16.1 breaking omnifunc completion in neovim #68764
Comments
What's odd is that autocompletion still works if triggered by entering a Still working out how to debug this, and the problem could exist elsewhere. But given that I can revert to |
gopls v0.16.0+ started to use @abennett Can you please share the LSP trace that includes the initialize message and the completion request/response messages (both failure case and successful case ( |
I'll try to get whatever you ask for! 🙇 |
From
From
I truncated items from each. |
Looks like the difference is the if item.textEdit and item.textEdit.range.start.line == lnum then |
|
So this is neovim's omnifunc not supporting |
and advertising the capability. I wonder if there's a minimally invasive way to suppress this capability in neovim. |
neovim/neovim#16909 and hrsh7th/cmp-nvim-lsp#53 (comment) may be related. The gopls uses |
Agreee. vim.keymap.set("i", "<C-x><C-o>", cmp.complete) |
Thank you fair bearing with me, @hyangah. 🙇♂️ |
gopls version
go env
What did you do?
gopls
tov0.16.1
.neovim
.<ctrl-x><ctrl-o>
neovim
throws an indexing errorgopls
versionv0.15.3
works as expected.What did you see happen?
Attempting to use
omnifunc
completion with<ctrl-x><ctrl-o>
result in the following indexing error fromneovim
.What did you expect to see?
Successful autocompletion recommendations without an error.
Editor and settings
Running
neovim
versionv0.10.1
.Logs
gopls
logs were empty. I can provide the lsp logs, but they're pretty brutal to read.The text was updated successfully, but these errors were encountered: