Skip to content

cmd/godoc: missing line breaks in indented section #6769

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
rsc opened this issue Nov 15, 2013 · 6 comments
Closed

cmd/godoc: missing line breaks in indented section #6769

rsc opened this issue Nov 15, 2013 · 6 comments
Milestone

Comments

@rsc
Copy link
Contributor

rsc commented Nov 15, 2013

What steps will reproduce the problem?

$ godoc runtime
...
    The GODEBUG variable controls debug output from the runtime. GODEBUG
    value is a comma-separated list of name=val pairs. Supported names are:

    gctrace: setting gctrace=1 causes the garbage collector to emit a single line to standard
    error at each collection, summarizing the amount of memory collected and the
    length of the pause. Setting gctrace=2 emits the same summary but also
    repeats each collection.
    schedtrace: setting schedtrace=X causes the scheduler to emit a single line to standard
    error every X milliseconds, summarizing the scheduler state.
    scheddetail: setting schedtrace=X and scheddetail=1 causes the scheduler to emit
    detailed multiline info every X milliseconds, describing state of the scheduler,
    processors, threads and goroutines.

What is the expected output? What do you see instead?

The actual comment says:

The GODEBUG variable controls debug output from the runtime. GODEBUG value is
a comma-separated list of name=val pairs. Supported names are:

    gctrace: setting gctrace=1 causes the garbage collector to emit a single line to standard
    error at each collection, summarizing the amount of memory collected and the
    length of the pause. Setting gctrace=2 emits the same summary but also
    repeats each collection.

    schedtrace: setting schedtrace=X causes the scheduler to emit a single line to standard
    error every X milliseconds, summarizing the scheduler state.

    scheddetail: setting schedtrace=X and scheddetail=1 causes the scheduler to emit
    detailed multiline info every X milliseconds, describing state of the scheduler,
    processors, threads and goroutines.

Where did the blank lines go?

This may be related to issue #6135, but that issue is already fixed and this is not.
@rsc
Copy link
Contributor Author

rsc commented Dec 4, 2013

Comment 2:

Labels changed: added release-go1.3.

@rsc
Copy link
Contributor Author

rsc commented Dec 4, 2013

Comment 3:

Labels changed: removed go1.3.

@rsc
Copy link
Contributor Author

rsc commented Dec 4, 2013

Comment 4:

Labels changed: added repo-tools.

@rsc
Copy link
Contributor Author

rsc commented Apr 3, 2014

Comment 7:

Can someone please fix this?

@griesemer
Copy link
Contributor

Comment 8:

Owner changed to @griesemer.

@griesemer
Copy link
Contributor

Comment 9:

This issue was closed by revision b8851ad.

Status changed to Fixed.

@rsc rsc added fixed labels Apr 3, 2014
@rsc rsc added this to the Go1.3 milestone Apr 14, 2015
@rsc rsc removed the release-go1.3 label Apr 14, 2015
@golang golang locked and limited conversation to collaborators Jun 25, 2016
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants