You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 8, 2022. It is now read-only.
Seems like it no longer works out of the box with go 1.11. I realise this isn't strictly an issue with luan/vimfiles but I thoght I'd document it here to save others the trouble. Until a root cause for the issue is discovered and fixed, I've found the following hack in my ansible script (to be run after vim-update) patches the issue:
- name: 'patch gocode: fetch'git:
repo: https://github.com/mdempsky/gocodedest: ~/go/src/github.com/mdempsky/gocodeforce: yes
- name: 'patch gocode: build'shell: '{{ item }}'args:
chdir: ~/go/src/github.com/mdempsky/gocodewith_items:
- 'if [ ! -f go.mod ]; then GO111MODULE=on go mod init; fi'
- 'GO111MODULE=on go build -o ~/.vim/gobin/gocode github.com/mdempsky/gocode'
The text was updated successfully, but these errors were encountered:
We ran into the same issue with the [deoplete] gocode panicked. Use :messages / see above for error details. errors as well. We fixed it manually by removing nsf/gocode from our GOPATH installing and building mdepmsky/gocode into our GOPATH.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
After updating go to 1.11 and then running update, I see the following whenever I try to edit a go file in vim:
gocode panicked
.I found the following in the gocode repo: mdempsky/gocode#48
Seems like it no longer works out of the box with go 1.11. I realise this isn't strictly an issue with luan/vimfiles but I thoght I'd document it here to save others the trouble. Until a root cause for the issue is discovered and fixed, I've found the following hack in my ansible script (to be run after vim-update) patches the issue:
The text was updated successfully, but these errors were encountered: