💾 Archived View for koyu.space › aartaka › public › this-post-is-lisp.gmi captured on 2024-05-10 at 10:49:14. Gemini links have been rewritten to link to archived content
-=-=-=-=-=-=-
By Artyom Bologov
I launch my IDE (well, actually, it's Emacs with SLY),
open up a Lisp file,
start up the console (we call it REPL here) side-by-side with the code,
and start programming.
I pick tab completions, add more procedures,
and iterate over the data.
Occasionally, some syntax error pops at me—some
stray comma or misspelled keyword.
It compiles, memory consumption, and code complexity is bearable.
A neat piece, I'd say.
Okay, that's a good blog post!
Let's publish it.
Maybe program some project afterward: I've got some time left before sunset.
So yes, this post (and other posts on this blog) are written in Lisp. Most of it is regular Lisp syntax:
Having these, I get a fancy blog post generated from raw s-expressions,
needing just a couple of syntax quirks to resolve.
Here's how it works:
To generate all the <meta> tags, favicons, and styles.
To create linkable sections.
To generate linkable plaintext paragraphs from raw Lisp code (you've seen these pilcrow signs after the previous paragraph.)
To shorten the overly verbose list and table markup (including this list you're reading.)
To generate anchor tags from the shortest possible links and text.
So here I am, bored before my IDE and uncertain about what to do next because my blog posts are already done compiling and deploying.
Maybe write some more?
Update December 2023: I switched to
C preprocessor for website generation.
This website is
and generated with the help of
You can view page sources by appending .h to the page URL.
Copyright 2022-2024 Artyom Bologov (aartaka).
Any and all opinions listed here are my own and not representative of my employers; future, past and present.