.@manton … the deal breaking screenshot:

What I would give for Sublime Text on my iPad.

Just found this, @manton, and diggin' it.

Hugo … your choice of which f$&king end oughta catch the ellipses could not possibly render your debug output more f$&king useless. Thanks, bro.

.@pratik

So, at some point I am gonna come back to the bookshelves plugin and touch it up with some of the techniques and best practices I've developed as I've created additional plugins. As it stands, I want to start with two things.

1. Check to make sure the plugin version as listed in the plugin.json is 6.0.0 so we can rule out an intermediate build that I corrected along the way.
2. Let's try replacing the use of the plugin parameter interface with the use of a data file stored in the plugin.

From Design → Edit Custom Themes select the plugin and create a new template with location data/plugin_bookshelves/bookshelves_data.toml.

Use the following as a starting point (where the asterisks in the description values are simply Markdown to render italics).

CoverWidth = 100
InitialView = 'grid'

[[bookshelves]]
key = "currentlyreading"
description = "*Books I am somewhat in the process of reading*"

[[bookshelves]]
key = "finishedreading"
description = "*Books I've managed to get myself to read*"

[[bookshelves]]
key = "wanttoread"
description = "*Books that gaze at me judingly from beneath the television, where they currently live, for having yet to crack their spine (f$&kers).*"

[[bookshelves]]
key = "didwanttoread"
description = "*Books whose gaze of judgement I've kinda become okay with as my interest in reading them has waned.*" 

Wait … so IE was such sh$te that rather than repair it, Microsoft totally rolled another browser called Edge? I suppose this means I can now tell IE compatibility to f$&k off guilt free?

Forget about the need to position that little f$&ker via Javascript … totes figured out the CSS.

F$&k it, I guess I'm gonna use Javascript to position this f$&kin' table of contents toggle button.

Sigh … and I guess it'd be kinda weird to have the section numbers and not inject them into the headers.

Whatever … I guess now we got section numbers.

Can't decide whether it would be worth introducing code to handle simply laying the TOC in to the left and keeping it visible when there is enough space. With the toggle button and swipe gesture working, I'm leaning towards stamping it as overkill.

.@pimoore A pair of my Swift repositories, for whenever you feel like looking at how beautiful a thing is the Swift language: SignalProcessing and MoonKit.

Implementing swipe gestures 'cause figuring out where to locate the TOC toggle is a pain in the a$$ on a phone screen.

Reminder, Jack … I do sh$t like this for no f$&king reason and forget about it the next month. I'm right down the street. Holler if you want your algorithm fixed … free of f$&kin' charge.

Processing audio signals to extract a chroma spectrogram for feeding into a neural network that predicts the likeliest of 74 frequency patterns forming common musical chords … what I was up to around this time last year. pic.twitter.com/1Dq9Y1Zan6

— Moondeer (@moondeerdotblog) December 20, 2021

A little closer.

A lot of styling and parameterization left; but, I removed all the injected Bootstrap so I'm calling this progress for the table of contents plugin.

Sooo … I need to work out the style and location of the button … but the table of contents plugin just passed the proof-of-concept stage.

Sooo … yeah … the plugin walkthrough I've been writing has grown so massive that I'm writing another plugin to make the walkthrough digestible.

By the way y'all, I just confirmed that the Micro.blog Conversation.js API (which I encapsulate inside plugin-conversation and then inject into my theme by including its plugin-conversation.html partial) plus Twitter linking via Bridgy is totally a thing.

This morning's random perusal of the Hugo documentation turned up a fix for the .Lastmod page variable defaulting to the .Date page variable value 100% of the time. Once again, the solution involves grabbing the reigns of your Hugo configuration using the config/_default/ directory. Create a template at config/_default/frontmatter.toml. Plop this line in as its content: lastmod = ['lastmod', ':fileModTime', ':default']. Just like that, you have yourself some accurate .PublishDate and .Lastmod values.

As many sections as this walkthrough is racking up, I think it's time to look into generating a table of contents.

.@manton … so I'm curious about what I can only assume are webmentions suddenly being sent via reply tweet today (the same day all my tweets got warnings slapped on them so something in the API must have shifted) and whether I oughta try displaying them (I only see notifications … not found in mentions).

.@pimoore I may write up a post with all the sh$t I could do in Swift that it pisses me off I can't do without it.

Sooo … @Apple … are we at the point yet where I can whip out Swift Playgrounds on my iPad (with this sick magic keyboard) and use my favorite (and f$&king superior to all as I've been rapidly finding out while being forced into using all this other subpar sh$te) language to create an action (say linting some Hugo theme or plugin files from my local Working Copy repository directory before pushing them to their origin and trying them out on Micro.blog) that can be woven into the Shortcuts ecosystem? 'Cause … if not … you're doin' it wrong.

Whoop, there it is. Refactored around the buggy a$$ Scratch.SetInMap and imposed some first-come-first-serve to stop the example code from f$&king with the walkthrough's card.