8000 Comment syntax highlighting problem with Go · Issue #380 · alecthomas/chroma · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Comment syntax highlighting problem with Go #380

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
ayoisaiah opened this issue Jul 14, 2020 · 0 comments · Fixed by #382
Closed

Comment syntax highlighting problem with Go #380

ayoisaiah opened this issue Jul 14, 2020 · 0 comments · Fixed by #382

Comments

@ayoisaiah
Copy link
ayoisaiah commented Jul 14, 2020

I'm trying to highlight the following snippet:

var char = 'न' // a rune literal
fmt.Printf("char is %d and its type is %T\n", char, char) // char is 2344 and its type is int32
fmt.Println(char == 2344) // true

Which gets rendered as this:

image

I suspect this is similar to #104, #106, and #142 in that EnsureNL should be enabled for the Go lexer.

This was referenced Jul 15, 2020
mrsdizzie pushed a commit to mrsdizzie/chroma that referenced this issue Jul 15, 2020
To allow proper detection of single line comments when there is no \n

Fixes alecthomas#380
mrsdizzie added a commit to mrsdizzie/chroma that referenced this issue Jul 15, 2020
To allow proper detection of single line comments when there is no \n

Fixes alecthomas#380
mrsdizzie added a commit to mrsdizzie/chroma that referenced this issue Jul 15, 2020
To allow proper detection of single line comments when there is no \n

Fixes alecthomas#380
mrsdizzie added a commit to mrsdizzie/chroma that referenced this issue Jul 15, 2020
To allow proper detection of single line comments when there is no \n

Fixes alecthomas#380
alecthomas pushed a commit that referenced this issue Jul 15, 2020
To allow proper detection of single line comments when there is no \n

Fixes #380
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant
0