@Hein Meling Thanks for the pointer, this actually helped. It gets
installed into `$GOPATH/bin`, which actually IS in my `$PATH`, but `which
godoc` shows `/usr/local/bin/godoc`. My `.profile` explicitly puts
`$GOPATH/bin` first, but somehow my $PATH starts with all sorts of crap
like
Trying and failing to use this. Help would be appreciated.
I'm working on a library module outside of GOPATH. The `go.mod` file is
present. The `go` commands such as `go test` seem to run in module mode.
But when I run `godoc -http=:6060`, it shows the standard library +
packages from GOPATH,
@Henrik
Comparing with general purpose watchers, being Go-specific makes it easier to
remember and lets it work well for Go projects with no configuration.
Mnemonically, it's invoked exactly like "go". It ignores non-Go files by
default. I can imagine the "go" tool eventually getting a "-w"
Good day gophers!
I want to highlight a certain Go development tool. My golleagues (sic) and
I have found it quite enjoyable to use: https://github.com/Mitranim/gow
"gow" is the missing watch mode for the "go" command. It's invoked exactly
like "go", but watches files and reruns the subcommand
Struct literals don't require keys, but `go vet` will complain about
unkeyed fields for a struct type from another package. It won't complain
about unkeyed fields for a struct from the same package.
--
You received this message because you are subscribed to the Google Groups
"golang-nuts"
