Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

vim 8.2, vim-go, vim-bazel, errcheck, & rules_go #14

Closed
BooneJS opened this issue Dec 26, 2019 · 1 comment
Closed

vim 8.2, vim-go, vim-bazel, errcheck, & rules_go #14

BooneJS opened this issue Dec 26, 2019 · 1 comment

Comments

@BooneJS
Copy link

BooneJS commented Dec 26, 2019

Hi,

I'm using vim 8.2, vim-go (latest), errcheck (latest), and vim-bazel (latest) on macOS Catalina. I'm using go_proto_library() to compile a protobuf, but vim-go flags my import as being not found despite Bazel successfully compiling it.

It's not that big of a deal because it's a warning I can ignore, but I was wondering if there's something quick and easy I can do to make it go away.

Thanks!

@malcolmr
Copy link
Contributor

This seems like a bug for vim-go, not vim-bazel? (Presumably you could compile the protobuf with command-line Bazel as well, and still see the same problem.)

In particular, perhaps this is fatih/vim-go#1328?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants