Post
Hyped up by the success of using a small Rust tool to turn an Org Roam garden into an uBlock Origin filter, without using Emacs, I'm considering writing a small Rust tool to do the same for Nam-Shub of Enki.
That way, it would no longer require emacs to build.
I could call it Pretty Good Pretty Garden Program Generator.
Now, the trick here is that I need to resolve noweb references for NSoE, and tangle out into different files and stuff.
I can do it in a few passes: first, I'll collect all the source blocks, and parse their arguments. Then, I'll iterate over all the tangle ones, and recursively collect all the refs. Then I tangle the files out.
Sounds simple!
@algernon Noweb, that's name I haven’t heard in a while. You guys doing literate programming?
Heh. Pretty much done in less than 200 lines.
It's not a general purpose Org Roam tangler, it's just barely enough to tangle out Nam-Shub of Enki.
And my CI now uses pgpgpg to tangle out NSoE's code from the Org Roam sources. Tests still pass.
I wonder how big the diff is between emacs-tangled and pgpgpg-tangled NSoE...
Pretty big, but I'm not seeing any functional differences.
The output could use a rotofmt (is there a rotofmt?), because the formatting, when exported as-is, is pretty terrible.
....what if I made the org roam -> html transform a little Rust tool, too?
I'm currently exporting to markdown with ox-hugo, and then turning that into HTML with Quartz, and... I do not really like Quartz, it has some stupid things, and is a pain in the ass to use. But it made it possible to have node dependency graphs, and backlinks, and whatnot, something most Hugo themes weren't supporting (because they were made for Hugo, and are unaware of Org Roam).
Buuuut... I could just build my own HTML, and implement all the features I'm missing. Like, <<foobar>> noweb references would be clickable, and if block has :noweb-ref blah, that'd be clickable too.
Aaand so on and so forth. Basically, I could fix all my pain points.
Why Rust? Why not Emacs Lisp? Emacs already has org mode, it has all the helpers and tooling and building blocks, no?
Well. I'm simply more comfortable with Rust than with emacs lisp, and it feels easier to do it in a language I use daily.
It also means that Emacs will not be needed to build the docs, nor the tangled out code, which will simplify it a lot. Yes, it will need Rust instead, but... it's easier to ship a static binary than emacs + a bunch of emacs packages, when it comes to building.
Huh, interesting. Something seems to eat all the ${foo} things in pgpgpg.
oh. it's Regex::replace. boo.
Install bonfire.cafe
Get the full app experience
