@akkartik My favorite discovery was that the Lisp and parser #TXR could work almost perfectly within the #Gemtext file format.

I could then run the parser in on itself and then it could work.

In simplest form it would recognise
`@(output)`
Gemini page

`@(end)`

The only distinction would have to use a `@@` to represent a `@` in a block.

Not bad having a language and a web protocol cooperating with only one character repetition being the syntactical distinction - narrower than regex flavours.

@ArneBab @mhoye Im investigating the potential of Mega makefiles:

Here is an example of a WIP:
https://git.sr.ht/~indieterminacy/1q20hqh_oqo_parsing_icemaqr/tree/main/item/Makefile#L531

From a chain of referenced keyvalues and components it builds an awk script that then emits a #TXR parsing-expression-grammar.

In this example keyvalues in a fedidocs repo for instance documentation:
https://git.sr.ht/~indieterminacy/1q20hqh_oqo_parsing_icemaqr/tree/main/item/owo-hwh_mq-mqm_searching-values-not-at_fediverse-actor.txr

Im tempted to make makefiles a repository of truth rather than databases.

I find that its particularly satisfying using keyvalues across languages