Part of my wants to ask about these random green dots attached to Micro.blog profiles … the other half really doesn't want to get caught up in badges (should that be what they are).
Where I'm at (actually … where I've f$&kin' been since this time last f$&kin' year):
When you waste an hour before you realize you were using
:=where you meant to use=(because having two separate assignment operators is poor language construction).Brunch time for the birdies.
Just realized this post really oughta be turned into one of those cute AF critter video stories with all the subtitles.
Let's take one of my common patterns in the other direction: if you’re reading this … and I brought you here with a cute a$$ puppy portrait … don't miss the monster post with 60-some cute AF media assets:
.@manton If you think folks might be more comfortable with YAML than TOML (when editing my data templates), you might could adjust the repository cloning logic to allow YAML files when under the
datadirectory. The only thing I find tricky about TOML is arrays of maps. No idea what regular folks would think.Side note: if Hugo supported comments within JSON files, I likely never would have learned TOML … but I think I like the top-level feel of it.
Sooo … since I figured out how to create my own Chroma style to use with Hugo 0.91's automagical syntax highlighting for fenced (and labeled) code, I've totally dropped plugin-prism. Other than my moondeer theme, the only other survivor is the shortcode for tricking Hugo into rendering its own code as example code rather than attempting to invoke it.
I figured I may as well generalize what was a shortcode for embedding shortcodes so that it would embed whatever TF I happened to want it to. So I did, calling this new rendition
preserve.The example output below tricks Hugo into not tagging the
+++lines that fence the front matter for a Markdown Hugo content file with the.errclass and into actual printing the shortcode in the content block below the front matter.+++ title = "Bookshelf" description = "Book collections" type = "bookshelf" +++ {{< plugin-bookshelves >}}To get this example to render in this little post looks something like:
{{< preserve "+++" >}} title = "Bookshelf" description = "Book collections" type = "bookshelf" {{< preserve "+++" >}} {{< preserve "{{< plugin-bookshelves >}}" >}}So what complex logic must one stick into the code for
layouts/shortcodes/preserve.htmlto get this all to work? All you need is this :{{ .Get 0 }}Side note: more trickery may actually be necessary for this shortcode to work outside of a code fence. Totally didn't work when I tried to render that list bit as inline code.
plugin-bookshelves (a README Experience)
A plugin for Micro.blog that creates a page displaying multiple bookshelves. Its code lives here.
If you're reading this on the Micro.blog timeline…
are y'all fairly comfortable with the idea of having your own custom theme for housing configuration files for my plugins or would it be less intimidating if a created another plugin whose sole purpose was to hold configuration files for y'all to edit?
The whole point here is persisting your configuration files. Whenever the directory holding the file (be it plugin or theme) updates, you'll need to have preserved your configuation before hand somewhere that you could copy and paste it back into the fresh directory.
My guess is that the contents of your custom theme are additive to whichever official theme you have selected, so, say, when @pimoore updates one of his themes and you have it selected as the base of your custom theme … you would get the benefit of the update without your files being touched.
A standalone plugin for configuration files would be less stable than that, updating whenever I feel it necessary to modify the contents of the configuration template files. It would, however, be more stable than editing the data templates inside their respective plugins, as these directories are likely to be updated whenever I need to adjust any of the files within the plugin.
P.S. Documentation chock full of hand holding forthcoming for all things configuration files (aka data template files … aka anything-in-my-plugin-under-the-data-directory).
Bet I just located the issue. I had an HTML comment between blocks in
layouts/post/single.htmlleftover from when I was double checking the microformat. Those little f$&kers are notorious for silently causing all kinds of issues.
Wanna generate the illusion of being capable of working in a bipartisan manner ahead of this year's elections? Let Biden have his little win when it comes to replacing number three in a six to three court.
.@manton here's some strange I'll try to get to the bottom of tomorrow.
With the previous theme reinstalled, everything builds … and the harmless errors are spawned by my conversations plugin.
With the latest theme version installed, the errors are no longer logged…
and it looks like everything builds (tags from homepage head)…
but … if you check the head tags for a post page…
the previous theme version's pages are there. It will be interesting to see if this new post will be permalinked … because it seems like what most likely happened was that everything looked right until I triggered the full rebuild for the first time with v180 installed.
.@harrisonjaime … if you're curious why TF this is happening start here (reading thoroughly):
and end here (following links and reading thoroughly:
The state of the plugins before I go about updating READMEs (thereby discovering whether everything is actually working):
Jenn (concerned by the current trend of our utility bill) over corrects with the updated heat setting.
.@manton Still curious about these push failures. Do these indicate a single failed push to some device or a full on failure? Did you and @maique receive the mentions from the the posts that failed to push?
I sure-as-sh$t hope you end this story with how those f$&king iguanacicles thaw out and walk it off.
.@manton If I end up selling you on the data templates for parameters … we could add an entry to
plugin.jsonfor registering the config files for display in the installed plugins list … perhaps even having them open in their own editor from there to make it less frightening.Okay … no more kars for kids until they stop pushing that little travesty and give us some f$&king kids that are actually playing their instruments.
My god … @SRuhle, @JakeSherman … apparently y'all still haven't read the memo:
Perhaps I was too quick to dismiss using Disqus on my site. Sure … I never received a single comment while I had the comment section displayed … but since removing it I've racked up seven comments … and apparently I've been missing out on casual sex with no strings attached.
Ok, how many of y'all read this in grade school?
Ok … how many of y'all read this in grade school and had to write an essay?
Ok² … but how many of y'all read this in grade school, wrote an essay, and the thesis of that essay was that the ends … in fact … do justify the means?
.@fobbio_bw Not sure if you've been keeping up (I consider the American Upside Down, American Anti-vaxxer, and Obstructionist Agenda the three must reads) … but I'm about to jump into finishing the story (The 19%ers being the guiding light out of the darkness).
Time to wrap up all this coding sh$te and get back to sociophilosophy.
cc @DomainJulian @medanthro @GrantNoland
Jason Cardwell
Creative nonfiction, art, poetry, apps, philosophy, music, wood work, knots, political culture critiques … some of the things I make.