-
-
Notifications
You must be signed in to change notification settings - Fork 7.7k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Custom Chroma Highlighter Lexer #10421
Comments
I think it's better to submit PR to chroma project for improvements than having weird custom lexers on themes :) |
Of course, chroma is obviously not willing to support small share of DSL (domain specific language) |
Naturally I can not speak for the project, but I was curious to know what domain specific language you'd like to include with your theme :) |
I'm make a AT Command set ebook, |
This functionality would also be useful for custom lexers that don't have wide usage purpose beyond the project they're used in. For example, adding a lexer for code blocks with the Similarly, this could be used for lexers of forked languages and those without enough adoption to make sense to maintain in chroma itself. Finally, I can see value in this for custom lexers for data structure examples, colorizing required configuration keys differently or underlining invalid values to enable textual representation of that information instead of having to include (and update every instance of when a change effects them) screenshots. |
This would definitely be helpful! At the moment, I forked Hugo and hard coded loading my DSL's custom lexer in. This obviously works, but it makes things like CI/CD a bit more painful as now I need to ensure everything is using that custom fork of Hugo. |
Will be very useful for our custom clis & tools |
Closing in favor of #11496. |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Allow user add custom chroma lexer, can improve theme render specific language (or new language) effect
e.g: AT command set
discuss: https://discourse.gohugo.io/t/41302
simple implementation: see #10419
The text was updated successfully, but these errors were encountered: