Skip to content
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

syntax highlight for go doc #40525

Closed
GopherJ opened this issue Aug 1, 2020 · 4 comments
Closed

syntax highlight for go doc #40525

GopherJ opened this issue Aug 1, 2020 · 4 comments

Comments

@GopherJ
Copy link

@GopherJ GopherJ commented Aug 1, 2020

What version of Go are you using (go version)?

$ go version
go version go1.14.4 linux/amd64

Does this issue reproduce with the latest release?

yes

What operating system and processor architecture are you using (go env)?

go env Output
$ go env
GO111MODULE="on"
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/cheng/.cache/go-build"
GOENV="/home/cheng/.config/go/env"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOINSECURE=""
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="/home/cheng/go/1.14.4"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/home/cheng/.goenv/versions/1.14.4"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/home/cheng/.goenv/versions/1.14.4/pkg/tool/linux_amd64"
GCCGO="gccgo"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD="/home/cheng/Projects/Ubudu/Rust/sbl_manager/dispatcher/go.mod"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build264484111=/tmp/go-build -gno-record-gcc-switches"

What did you do?

  1. go doc time

What did you expect to see?

syntax highlight

What did you see instead?

no syntax highlight

@GopherJ
Copy link
Author

@GopherJ GopherJ commented Aug 1, 2020

There is a closed issue:

#13178

It's really surprising that some members of golang think it's not useful to have syntax highlight. At least it helps to read....

image

@mvdan
Copy link
Member

@mvdan mvdan commented Aug 3, 2020

Please clarify how this issue is any different than the previous one. Simply disagreeing with an issue's outcome doesn't really add anything meaningful to the discussion. It most likely will be closed as well, as a duplicate.

If you want to make a strong case, what new are you bringing to the discussion that wasn't already brought up in the previous issue?

@mvdan mvdan added the WaitingForInfo label Aug 3, 2020
@GopherJ
Copy link
Author

@GopherJ GopherJ commented Aug 3, 2020

@mvdan Let's close it then since go isn't that open to community's requests.

@GopherJ GopherJ closed this Aug 3, 2020
@mvdan
Copy link
Member

@mvdan mvdan commented Aug 3, 2020

To be clear, that's not what I said. I only asked you to make a stronger case so that this issue isn't closed as a duplicate. It's your choice to draw your own conclusions or close the issue entirely, though :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.