Pontus Leitzler

Thanks for the report! I did take a quick look at the logs but couldn't see anything obvious going on in govim. The fact that you can continue to use...

That particular log looks like a panic in `gopls`, and `govim` doesn't handle crashed gopls that well so each interaction has a delay of 30s and it makes vim totally...

Log with go1.13.x: https://gist.github.com/leitzler/516076bd6f0e965424cd9f1d33fc0b1f

Could be related to https://github.com/golang/go/issues/37741 (also see https://go-review.googlesource.com/c/go/+/223240/)

#828 won't solve anything, but hopefully provide more details (and not force the tests to timeout). (Narrator: It didn't.)

The wiki is probably out of date on several places :(. But this particular feature seems to be missing on the gopls side as per golang/go#31150.

The `ExpermientalMouseTriggeredHoverOptions` aren't passed to vim verbatim today, since there is no way to specify a value relative to the mouse position. The position passed will have the cursor/mouse position...

Let me know if the workaround doesn't work for you @jbpratt

Just fyi - the failed test looks like #884 / golang/go#39646

Got any updates on this one? I'm just about to add CodeLens support and it would be nice to use the `go.mod` features from there as well.