Thanks to all for assistance with this!
Got it working with (perhaps) the most recent version - though once again
it looks to have moved from the path(s) mentioned above. Part of my
problem was not looking specifically for the "Third Party" section since
before my code had all been lumped in
Assuming a recent enough version of `godoc`, running it from within a
module should include the documentation for the standard library (standard
library section), that module, and all its dependencies (third party
section)
Expected output should be similar to:
$ godoc
using module mode; GOMOD=/
Clarification. As mentioned earlier, $GOPATH is supposed to go away in the
(possibly near) future so one of my main goals is to get it working outside
the $GOPATH tree. At present my solution has been to copy my source tree
(about 4 GB) to a "non-module-aware" go ecosystem on a different machi
I found you had to cd to each directory with a .mod file and run it there.
A global option would be nice to know about.
--
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 emai
On Sat, Mar 27, 2021 at 4:55 PM Hotei wrote:
> Could use a little help figuring out how to attack the following problem:
>
> I normally run godoc locally with $godoc -http=":6060"& and then browse it
> with chrome.
>
> Many years ago that method broke for a while as godoc was "reinvented"
> but
Could use a little help figuring out how to attack the following problem:
I normally run godoc locally with $godoc -http=":6060"& and then browse it
with chrome.
Many years ago that method broke for a while as godoc was "reinvented" but
then it came back pretty much the same as before. A few
