Closed stefanos82 closed 1 year ago
I'm not familiar with those plugins, but I noticed that completor.vim
use gocode for completion. gocode
is unmaintained and the Go community moved on from it several years ago. In addition, vim-mucomplete claims to try a number of completion engines until one matches. That could also be a problem, because vim-go's completion is asynchronous already, and Vim 8.2.0614 added some restrictions to how windows can be changed while completions are in progress. Those restrictions were somewhat loosened in 8.2.0670, but not fully IIUC.
I'm not sure there's anything that can be done about this, nor am is it clear if the problem is with vim-go or with those other plugins.
I'm not familiar with those plugins, but I noticed that
completor.vim
use gocode for completion.gocode
is unmaintained and the Go community moved on from it several years ago.
Yep, but at the bottom of README there's this:
That saved me from having that nightmarish behavior.
I guess I could close the ticket now because I said to myself, "let's test it for a while now and if everything goes well, come back here and close the ticket".
Seems like I forgot to do that :laughing: my bad!
All well now, thank you for your reply @bhcleek :+1: much appreciated!
I'm using Vim 9.0 and I have noticed a rather peculiar behavior that takes place at random.
I combine
completor.vim
withvim-mucomplete
and makes Go development work really smooth.The only problem is the following errors
that take place when I have
let g:mucomplete#enable_auto_at_startup = 0
enabled; here it's disabled to prevent the aforementioned errors from taking place.Seems like it happens while typing (thus in Insert mode) which means it attempts to fetch data from an unimported package / module.
Is there anything I could do to remedy this problematic behavior?
It interrupts my thought process as I attempt to solve a problem while testing code.
Please advice.
Specs
Vim info: