Closed aitva closed 4 years ago
@aitva thanks for the report and for providing a repro. Apologies for the delay in replying to this.
I just tried the repro against govim
35c32a5 and Vim v8.1.1967
but was unable to repro this.
Are you able to consistently repro this? If so, it might be worth us raising as a Vim issue
Closing as we've received no further reports of this. We can always re-open in case there is something specific with govim
usage that causes this.
What version of Vim/Gvim are you using?
Vim/Gvim version
What version of Go are you using (
go version
)?What operating system and processor architecture are you using (
go env
)?go env
OutputWhat version/commit of
govim
are you using?commit 35c32a559f17b415543c62f4494c02de795a0c08
What is the output of
:messages
in Vim?I cannot access
:messages
, Vim was frozen and I had to kill it.Do the Vim channel,
govim
orgopls
log files show anything interesting?I had a look but found nothing fancy.
How did you install
govim
?vim-plug
What did you do?
I was manually renaming a small package with a few types. Once I hit
:w
Vim completely froze.I reproduced the bug in the govim repo:
cd cmd/govim/internal/golang_org_x_tools
mv lsp lsp-test
vim -p lsp-test/code_action.go
package lsp
topackage lsp-test
:w
As a note, Vim returns a segmentation fault once killed:
What did you expect to see?
Vim saving the file as usual.
What did you see instead?
A frozen / unresponsive Vim, I had to kill it from another prompt.