My mistake: not only was I not up to date, I was running somebody else's unmerged PR that added vendor support. Looks good now!
On Tue, Jul 19, 2016 at 8:34 AM, roger peppe <rogpe...@gmail.com> wrote: > On 19 July 2016 at 15:35, David Glasser <glas...@davidglasser.net> wrote: > > On Jul 19, 2016 3:16 AM, "roger peppe" <rogpe...@gmail.com> wrote: > >> > >> On 15 July 2016 at 16:44, <dglas...@gmail.com> wrote: > >> > On Thursday, July 14, 2016 at 10:34:36 PM UTC-7, bradfitz wrote: > >> >> > >> >> goimports has been updated. > >> >> > >> >> If you've been frustrated by its speed lately, run: > >> >> > >> >> $ go get -u golang.org/x/tools/cmd/goimports > >> >> > >> >> ... and things should be much nicer. > >> >> > >> >> Details at https://golang.org/cl/24941 > >> > > >> > > >> > In addition to all the performance work, I'm excited to see: > >> > > >> >> * when adding imports, add names to imports when the imported package > >> >> name > >> >> > doesn't match the baes of its import path. For example: > import > foo > >> >> "example.net/foo/v1" > >> > > >> > if for no other reason than that godef works better with these imports > >> > (https://github.com/rogpeppe/godef/issues/40). > >> > >> FWIW that particular issue isn't usually a problem for the > >> way that most people use godef (as an editor plugin), as > >> it only affects you if you use it directly on the command line, > >> something that I assume is fairly unusual. > > > > Huh, I do see that issue when using godef in emacs. But maybe either my > > godef or its emacs integration is out of date. > > Try updating your godef. If you still see the issue, get back to me, as > AFAIK it > *should* be fixed! > -- glas...@davidglasser.net | langtonlabs.org | flickr.com/photos/glasser/ -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
