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

Chapel support in highlight.js? #16454

Closed
bradcray opened this issue Sep 24, 2020 · 5 comments
Closed

Chapel support in highlight.js? #16454

bradcray opened this issue Sep 24, 2020 · 5 comments

Comments

@bradcray
Copy link
Member

It appears that Stack Overflow is changing from Google Prettify to highlight.js, yet it seems that there is no Chapel support in highlight.js. This task is about adding Chapel support, either officially within highlight.js (ideally) or as an externally supported package (though... if we were to do this, would this mean that we wouldn't get highlighted on SO?)

@ghost
Copy link

ghost commented Oct 15, 2020

I would like to work on this

@bradcray
Copy link
Member Author

That would be great! I don't think we know much about highlight.js yet on my team, but it looked pretty well documented from what I did see. Let us know if/how we can help.

@bradcray
Copy link
Member Author

It turns out that Discourse uses highlight.js as well, so this would be a double-win now that we have https://chapel.discourse.group/

@bradcray
Copy link
Member Author

I'm taking a look at this as a study break this afternoon since the previous person indicating interest is now a ghost.

@bradcray
Copy link
Member Author

bradcray commented Nov 2, 2020

I've added some initial Chapel support for highlight.js as a third-party package in highlightjs/highlight.js#2806 and https://github.com/chapel-lang/highlightjs-chapel. Unrelated to the PR and repo, I enabled Chapel highlighting for Discourse through the site's admin interface. It looks as though enabling Chapel highlighting at StackOverflow will be a more significant effort as a third-party package, but that will be something to look into next.

The initial grammar I did is not particularly robust or complex, and could probably be improved, but I'm going to close this issue based on the fact that we now have some support.

@bradcray bradcray closed this as completed Nov 2, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant