Will Faught

Hi @flyingflo, thanks for your report. I added that behavior so that you don't get huge heading sizes when only using one heading level like `## Foo`. It seems that...

>However, it might be better to adapt bootstrap's h6 style. @flyingflo I'm not sure what this means. Are you suggesting an idea? I see that you changed that webpage to...

@flyingflo @pbj-writes @jezcope Sorry for the delay responding. I decided this behavior would be unexpected and perhaps unwanted for a not-insignificant number of users, so per @jezcope's suggestion, I turned...

(@ianlancetaylor [suggested](https://groups.google.com/g/golang-nuts/c/Yt6UGhPMXDs/m/KAqja9l2AgAJ?utm_medium=email&utm_source=footer) I repost here. Happy to move this to a new issue if needed.) go env doesn't seem to work well with GOTELEMETRY: ``` Despite showing up an an...

>I don't think we can eliminate go telemetry on -- my understanding is that we need the current language to be printed immediately when the user enables telemetry. @findleyr It...

>but https://github.com/golang/go/issues/67111 was accepted and implemented and shipped, and it is very unlikely that we'd remove a subcommand, especially for superficial reasons. If the handling of the go telemetry mode...

>That's an interesting idea, but beyond the scope of this issue. I'll file a separate issue. Thanks. >If we were to support go env -w GOTELEMETRY=on, then we'd need to...

>Hmm. I think I'd prefer a model where the "local" and "on" data is separate, as it seems a bit hard to wrap one's head around GOTELEMETRYSTART as an environment...

Sounds promising! The new interfaces are great. Making Client a mockable interface would greatly ease testing. When I test a component that uses this client, the only thing I really...

Please consider enabling perf customization as discussed in #32.