[go-nuts] Re: godoc (golang.org/x/tools/cmd/godoc) has become module-aware
@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 `/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:`. It never occurred to me to check. Thanks for the suggestion! I'm off to figure out what's causing this... Meanwhile, `$GOPATH/bin/godoc` works as expected and even announces running in module mode. The documentation of the local module is present on the webpage. Thanks! -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/1e7b3863-fca3-47ff-ab6a-5dc710a66838%40googlegroups.com.
[go-nuts] Re: godoc (golang.org/x/tools/cmd/godoc) has become module-aware
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, failing to include the current module. I've updated `godoc` via: go get -u golang.org/x/tools/cmd/godoc However I'm unable to check the installed `godoc` version, as it lacks such a subcommand, so I can't be sure if the installed version actually includes module support. The documentation doesn't give examples or mention modules at all. Any suggestions? -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/8897eda1-db92-405d-b4fc-a98f693b2619%40googlegroups.com.
Re: [go-nuts] New development tool: missing watch mode for "go"
@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" flag that replaces "gow" as-is. In addition, every other tool I've tried had AT LEAST one of these problems: * noisy output * delays in the file watcher, usually not configurable; this drives me crazy * creates garbage files * eventually needs configuration files * unreliable * can't stop and restart the subprocess * can't clear the terminal on restart * complex codebase, unreasonably difficult to hack on That's just my experience. -- 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.
[go-nuts] New development tool: missing watch mode for "go"
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 on changes. Common use cases: gow run . gow test gow vet Clear terminal on restart with "-c": gow -c run . Another fancy feature: hit "^R" to restart the subprocess. See "-h" for more options. I hope others will find this equally enjoyable. Feedback and requests for improvement are welcome. -- 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.
[go-nuts] Re: struct literals require keys on GAE?
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" 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.
