> On Jun 15, 2026, at 22:58, Ihor Radchenko <[email protected]> wrote:
>
> Perry Smith <[email protected]> writes:
>
>> Another item to consider: org-export-before-processing-hook is before the
>> includes and org-export-before-parsing-hook is after the includes but also
>> after the macro processing. I think I could leverage a hook after the
>> includes but before the macro processing. Then I could find whatever
>> pattern I wanted to search for and tweak it.
>
> Could you elaborate about use case? It is easy to add more hooks, but
> not clear if we really need to.
The use case is to be able to do a global search and replace after the
includes. I could search for †foo† and replace it with {{{san-serif(foo)}}}.
Then the macro engine would kick in and do whatever that macro said. Macros
are not that powerful but Babel is and it has a lot of abilities that could be
leveraged. I have call_menu(term=“ISO speed settings”) that goes through a
table, find the matching string and pulls out other information in the table.
Babel already had all the smarts on how to process tables. I’d like to easily
tap into that but still clean up the clutter of the call_menu( … ).
