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 weeks ago I converted a lot of old code to use modules. Now that I've converted my local packages tree to modules I find that the same godoc code I've been using with no problem before can only find the packages in the official source 1.16.* tree. I don't know if this is a bug or a feature but if possible I'd like to find a way so that the old method still works. Is there a work-around? Sorry if this ground has been covered before. There's no error message to reference, just the absence of my source (and that of others from golang.org, github.com etc) in the listing. It's possible I'm not using the latest & greatest godoc but it has moved around a bit the last few years so I'm not 100% sure what the canonical version is right now. Any help appreciated. I also wish godoc handled programs (as opposed to just packages) but I can work around that where necessary. Thanks in advance. David -- 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/19a7749e-31cc-4308-93f1-e9e436a75e22n%40googlegroups.com.
