gocode: Doesn't auto-complete paths of exclusively vendored packages

@dvcrn For currently edited package gocode uses source files and if it doesn’t pick up new files it’s a bug, but if you add a file into a separate package and use it from another package, that separate package should be compiled first. Gocode has autobuild feature (see README.md), but I wouldn’t guarantee it would work. All it does is it runs go install before autocompletion. You can also use third party FS watcher which compiles stuff for you. In my opinion if you do something that requires you to jump from one package to another, you do it wrong. But that’s only my opinion, I understand people have different workflows. One day gocode will parse source files, but I can’t tell when it happens, maybe next year, maybe even later. Once I had a plenty of time to work on gocode, now I don’t have time at all and if I have some, I spend it on different projects of mine, often not even related to Go.

Sorry, I probably misunderstood your comment. I still don’t understand what you meant by, “operates outside of user set GOPATH”.

govendor populates the standard vendor directory with dependencies. It is more like gvt and glide than gb.

You missed what I said. You need to compile the lib for gocode to pick it up. Gocode doesn’t work with source files.

Cutting the string until “vendor/” would make sense…

El 14 de octubre de 2016 9:54:02 GMT-06:00, Anmol Sethi notifications@github.com escribió:

That is exactly what should be happening.

You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/nsf/gocode/issues/381#issuecomment-253841510

Sent from my Android device with K-9 Mail. Please excuse my brevity.