Compatibility with gopls?

[davidyoung604]

Hi all. I only found out about this package today, after setting up a new machine with this version of kickstart, so I apologize in advance for not being super familiar with how blink does things. I tried to make my way through the doc site, but nothing seemed directly applicable in the end.

I'm having an issue with imports in Go files, whereas I didn't have this with the previous cmp solution included in kickstart. The issue is that if I start typing a common package name (e.g. types) the completion list only shows me multiple entries for types with no additional data (i.e. [types, types, types]). I eventually found out that I could force it to show the full package path (e.g. go/types, github.com/foo/bar/baz/types) if I turned on documentation.auto_show. The downside of that approach however, is that I have to go through each entry in turn to see what the "documentation" value is, rather than seeing the full list and jumping through it. Also, this isn't something I'd consider to be documentation, so if I hadn't been actually intending to turn on documentation, I wouldn't have found this is where the package info was hiding.

Videos I've seen of people using blink for other languages seem to have far more clear completions, including for imports, so is this maybe an issue with gopls? Or is there something on the blink side of things that can be done for this? Thanks in advance for any guidance you might be able to offer.

[soifou]

There is an opened issue for this: #1610

Until it is resolved, you can try the following workaround: #1317 (comment)

[davidyoung604]

Wow, that's just plain embarrassing for me - it's even the same package name in the workaround you linked. But it works, thanks!