@kexpmusicbot@mastodonapp.ukπΊπ¦ #NowPlaying on KEXP's #MorningShow
Prism Shores:
π΅ I Didn't Mean to Change My Mind
#PrismShores
https://prismshores.bandcamp.com/track/i-didnt-mean-to-change-my-mind
https://open.spotify.com/track/2KLOJo0lQdAPgkAllFFEW3
@kexpmusicbot@mastodonapp.ukπΊπ¦ #NowPlaying on KEXP's #MorningShow
Prism Shores:
π΅ I Didn't Mean to Change My Mind
#PrismShores
https://prismshores.bandcamp.com/track/i-didnt-mean-to-change-my-mind
https://open.spotify.com/track/2KLOJo0lQdAPgkAllFFEW3
@mgorny@social.treehouse.systemsTotally normal workflow:
I work on documenting #Jinja syntax used in #CondaForge recipes.
#Prism doesn't have one. But Internets suggest Twig would work instead.
#Docusaurus. But there's a workaround.
https://github.com/facebook/docusaurus/issues/8065
So I copy the code over to the project, fix it and while at it, rename it to "jinja" and adjust a bit.
But then, highlighting Jinja expressions alone looks pretty bleak, so let's combine it with YAML⦠Hmm, that actually doesn't work that well, needs some more adjustments. And before you know it, I have a pretty new Jinja highlighter, and a recipe highlighter that combines Jinja expressions, YAML, v0 recipe selectors, v1 if:/skip: conditions, and also highlighting shell / cmd variables for a good measure.
https://github.com/conda-forge/conda-forge.github.io/pull/2790