With bugs!

Journal Entries

  1. Bringing Visual Studio Code Syntax Highlighting to Jekyll: Day 4

    Goals So… my last day of working on this was interrupted by the battery in the display of my Surface Book deciding to bulge, requiring me to go through a several day process of safely backing it up, finding my replacement, and upgrading my replacement to the latest Windows 10. The good news is I did recover a lot of context. The bad news is that’s about all I did.

  2. Bringing Visual Studio Code Syntax Highlighting to Jekyll: Day 3

    Goals Wow, it’s been a long time since I’ve made time to work on this. Almost a year. Since I don’t really know where I left off, my primary goal for today is to just try and recover all of my context. Secondary goal is to get some syntax highlighter wired up. Investigation Kramdown From reading my past journals, I see what the code needs to look like. It’s been almost a year, and kramdown may have changed.

  3. Bringing Visual Studio Code Syntax Highlighting to Jekyll: Day 2

    Goals I feel like I made good investigative progress yesterday, but not so good code progress. That’s okay. I was burned out from my Friday night activities (not what you think) and needed recovery time. I feel better today, and although I have some housework I should do, I’m feeling a bit ambitious. I’d like to complete the primary investigative work today, which means I need to accomplish the following two things:

  4. Bringing Visual Studio Code Syntax Highlighting to Jekyll: Day 1

    Motivation Since this is a programming blog, there is a 100% certainty that at some point I will need code snippets in some blog posts. I’ve never really liked online syntax highlighters, as I find most of them too bland. I do like the syntax highlighting I get with Visual Studio Code, though. (Especially the Dark+ theme.) I tried to port the style of that theme to Rouge (Jekyll uses kramdown, kramdown uses Rogue), but the supported syntax elements and regular expression based parsing didn’t make for enough specificity in the generated HTML for the stylesheet to match on.

RSSSubscribe to this journal