You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After some digging, I found out that the 'catppuccin-macchiato' style accidentally uses color instead of background-color for its line highlighting. I.e. it uses
.chroma .hl { color:#494d64 }
but should be using:
.chroma .hl { background-color:#494d64 }
So if I switch this (by jumping through some hoops), it looks as expected:
I know this might be the wrong repo for filing this (the bug could be in the Chroma or even in the Pygments repo). Unfortunately, I'm no Go developer - so I couldn't really describe the problem in the other repos. So my hope is - if you find this bug is not a Hugo bug per se - that you'll file a bug repo in the appropriate repo. Thanks :)
What version of Hugo are you using (hugo version)?
$ hugo version
hugo v0.121.2-6d5b44305eaa9d0a157946492a6f319da38de154+extended windows/amd64 BuildDate=2024-01-05T12:21:15Z VendorInfo=gohugoio
Does this issue reproduce with the latest release?
Yes
The text was updated successfully, but these errors were encountered:
It was an oversight at my end @skrysmanski. Until, the embedded chroma version is bumped again, you could manually override the chroma styles as mentioned here. Thanks for catching it @jmooring.
When selecting 'catppuccin-macchiato' as highlighting style like so:
And then writing some code with highlighted lines:
Then the two lines are not highlighted properly:
After some digging, I found out that the 'catppuccin-macchiato' style accidentally uses
color
instead ofbackground-color
for its line highlighting. I.e. it usesbut should be using:
So if I switch this (by jumping through some hoops), it looks as expected:
I know this might be the wrong repo for filing this (the bug could be in the Chroma or even in the Pygments repo). Unfortunately, I'm no Go developer - so I couldn't really describe the problem in the other repos. So my hope is - if you find this bug is not a Hugo bug per se - that you'll file a bug repo in the appropriate repo. Thanks :)
What version of Hugo are you using (
hugo version
)?Does this issue reproduce with the latest release?
Yes
The text was updated successfully, but these errors were encountered: