-
-
Notifications
You must be signed in to change notification settings - Fork 5.7k
Much more conservative highlighting for 1.12 #58408
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
Much more conservative highlighting for 1.12 #58408
Conversation
Following a few vigorous complaints about the highlighting scheme introduced by JuliaSyntaxHighlighting, I've pared back the default behaviour to something much more conservative.
3881b92 to
9a46bf5
Compare
|
I think this is an improvement over both 1.11 and current 1.12 behaviour. |
|
Is it possible to keep just the type-highlighting? Specifically in this part: ncodeunits(s::AbstractString) -> Intbut not in the general code examples (i.e. only the documented signatures) |
Hmmm, it's possible but not particularly easily I'm afraid. I think we'd need to implement a new inferred code block "language" like |
|
Is JuliaSyntaxHighlighting converting the |
|
Yeah that's not ok. If that can't be sorted out we'll have to drop coloring of chars and strings. |
That came from #57012 |
Urgh, when did that start happening? Good catch, I'll look into it… |
Ah. Should that be backported? |
|
Did this ever get in or was it just closed when the backport branch got merged? |
|
Looks like this PR was just closed by the targeted backport branch being deleted. I'll put up a new PR with the fixed char highlighting in the next few days. |

Following a few vigorous complaints about the highlighting scheme introduced by JuliaSyntaxHighlighting, I've pared back the default behaviour to something much more conservative. Now the only highlighting applied is:
Old behaviour (1.11)
Nightly behaviour
Behaviour here