Macro

Those four core functions handle the formatting logic.

Macro.postwalk just maps the hundred and seventeen names to those four structural rules.

So what does this all mean? We just bypassed writing a hundred and thirteen macros.

How does that actually change a developer's day-to-day workflow?

You just update the text file.

You literally just add twenty words to your flat text file, recompile, and your entire DSL instantly supports the new specification.

The cleanliness of how Macro.postwalk manipulates the tree is unparalleled.

Okay, but with all this invisible code injection, AST manipulation, and domain language creation, we have to talk about the dark side.

So, you could give them access to, let's say, Obsidian locally and you guys could communicate notes back and forth and whatever.

The problem being markdown files have a fair bit of functionality in them that it sounds like was not Macro-y.

Yeah.

And the other thing is like there's this concept of a vault with Obsidian, but you also can open files outside the vault.

You should be able to drill down in the change to see exactly what impact.

And I'm happy because in the past, we used to do it with Excel, sometimes with Macro.

So it was more time consuming.

And