Non-fenced code fragments (using backticks in Markdown) will now be
formatted with a background color, padding, and a border. I was
avoiding this for some time, but most of my writing also didn't have a
whole lot of code in it. That's changing with the article I'm writing
now, and it really is much more clear with this styling; it can
otherwise be more difficult than necessary to tell where a command
starts and ends, and the monospace font can sometimes be too sublte of
an indicator for shorter text, or text that uses characters that are
harder to distinguish.
We're finally in an era where this is natively supported on all major
browers and platforms, at least on modern browsers. I've been waiting
for this for...nearly 15 years now? My go-to previously was Mathjax.
I guess I should remove my IE11 support in CSS, then, huh?
Or maybe leave it around as an easter egg / relic type of thing.
The article I'm working on makes (very) heavy use of the `details` HTML
element, and nests them. Making sense of the article without
indentation is difficult and torturous.
This has complicated the prefmt script enough that it really ought to be
extracted into something else. I'm admittedly disappointed that I've
had to do this much work with it, because it completely sacrifies any
hope of portability. Oh well, that's not even a design goal, though
it'd be nice to be able to have the preview of Markdown files make sense
in e.g. Forejo.
I figured I'd have the least numbre of problems with nesting if I strip
whitespace prefixes based on the current level of nesting. To avoid
surprises, I enforce expectations statically---it will not compile
without proper nesting.
To reduce the potential blast radius, I'm doing this only for `details`
for now; it'll expand later on. I did diff the output of older articles
to make sure they were unaffected.
I previously included hard-coded CSS. Pandoc will apparently generate
what is needed for the page, but I didn't have that included in my
template.
I chose Tango out of a nearly 20y personal preference now, ever since I
used the Tango Icon Theme in Ubunutu Dapper Drake (6.06), my introducing
to GNOME/GTK. I might have used Breezy, too, I don't recall.
Prior to that I think I used Mandrake (before it was Mandriva), which
was the first distro I tried, after my laptop's HDD died and I was
awaiting a replacement (couldn't run Windows without a HDD).
...anyway.
Previous I had been using pandoc 2.9.2.1, available through the Debian
repositories. I installed 2.19.2 through Guix.
The biggest issue I ran into was wrapping of the output, which messed up
my klugy post-processing scripts that expected `h1` tags to have their
attributes all on the same line. The `--wrap none` flag resolves that.
I diff'd the webroot before and after these changes. The primary
changes were related to footnote classes, the recognition of fancy
quotes in a couple new situations, and new classes introduced to source
code listings. I'll have to investigate styling them, since I haven't
visited the CSS for that in quite some time.
When I introduced TeX-style ties to `post2html`, a couple parts of this
article were broken.
I ought to check whether other articles are broken, or rather write a
script to list occurrences, but, it's late, and I want to get this
resolved.
It's been a couple of years since this page has been updated. It has
received a cleanup---removing information that I find to be unnecessary
or redundant---and some minor updates.
Note that the removed phone number has not been in use for at least a
couple of years; I apologize for anyone who may have tried to reach me,
however unlikely that is. I am not replacing it with a working number,
since I don't want unsolicited calls.
I decided to update all of this in a single commit rather than
commenting on and rationalizing each individual change.
This network-level concern is not appropriate for this repository.
When I originally added it, my thought was that I'd be helping to
protect the privacy of people who cloned the repository. But that
responsibility does not belong here.
I don't need to proxy through Tor anymore through software, as I have
since handled privacy-related networking concerns elsewhere (whether it
be at the router or host OS level).
This removes the cgit configuration and added redirects. I'll check the
404 log and determine if I should add others in the future, if it's
worth the effort.
I've been essentially inactive publicly for a couple of years. I'll
have more information in time, but the past couple of years have given
me a lot of time to reflect and redefine parts of myself.
This is step toward surfacing.
Mastodon was far too much load on my server. And while the sever is
just a dinky like 1-vCPU VPS, it shouldn't _need_ any more than that; I
barely use Mastodon and I will not upgrade my server (and incur greater
costs for it).
Pleroma is compatible with Mastodon (based on ActivityPub) and much more
efficient. We'll see how I like it. My account transfer is happening
right now; the fediverse is a wonderful thing. :)
For some more context: Mastodon was fine for years, but after Musk's
takeover of Twitter and increased adoption of Mastodon, my sever became
burdened by all these new instances, despite _my_ use of it being
effectively nothing.
This notably introduces The TAME Programming Language Living Document,
and effort to begin to formalize the language I've been working on over
the past decade on-and-off for my employer.
It's pronounced "new"plot, where "gnu" refers to the animal, pronounce
"new", not GNU, pronounced "guh-new".
I did not know this at the time.
http://www.gnuplot.info/faq/faq.html#x1-70001.2
Older versions of Gawk did not mind an empty string as the third
argument, but newer versions complain:
warning: gensub: third argument `' treated as 1
Figures will have margins on the left and right sides by default, unless
explicitly denoted "inline". The caption will also be a lighter typeface
rather than bold. When the figure caption appears at the bottom, it will
have a top border.
I'll be using this to show example HTML code and then output it as actual
HTML to be rendered as part of the article. Otherwise the HMTL has to be
duplicated and maintained in multiple places.
An alternative is to include a file, but that is much less convenient for
smaller snippets.
I hate Markdown as a format for disciplined writing, especially when I want
macros (mostly semantic), indexes, and such. I was originally going to use
LaTeX with Pandoc, but it lacks support for inline HTML and such, and I do
not want to distract too much from the work that I want to be doing.
Mike Gerwitz