Hugo 0.28 brings “high-speed syntax highlighting” to the party, via Chroma, “a general purpose syntax highlighter in pure Go” and “based heavily on Pygments”.
Using the now default Chroma highlighter is covered in the updated syntax highlighing documentation. Notably, there are config options for emulating particular Pygments setups.
Both notes are interesting, so quoting them verbatim:
- Hugo now uses Chroma as new default syntax highlighter. This should in most cases work out-of-the box or with very little adjustments. But if you want to continue to use Pygments, set
pygmentsUseClassic=truein your site config.
- We now add a set of “no cache” headers to the responses for
hugo server, which makes the most sense in most development scenarios. Run with
hugo server --noHTTPCache=falseto get the old behaviour.
Note: there was a performance issue with
noHTTPCache, and excluding those headers is the default in 0.29, once again.
My one concern is the accessibility of code blocks saturated with
But what happens if the HTML is taken and rendered elsewhere with a bunch of crufty elements? Does that throw a wrench into the works?
Bonus: I fixed a typo in the blog post! But I had to sign a CLA. Meh.
This is a companion discussion topic for the original entry at https://interi.org/notes/hugo-0.28/