See the variables org-export-before-processing-hook and
org-export-before-parsing-hook.
You can put something like this in a noexport tagged build heading in
your document. Here I run head on the org-file to just get the first
three lines. you can replace that with your external filter.:
Thanks Ken.
Yes, at first I was trying to accomplish my task with Macros, but after
finding out that I could run the whole Org file through a pre-filter, I
realized that this would be a much cleaner and easier way rather than
having multiple types of macros or code blocks. So now I'm trying
Hi Josh,
On 2019-03-10 at 23:37 +0100, Josh wrote...
> I am new to emacs and orgmode. I spent the last couple days reading
> most of the docs before diving in,
Welcome!
> but I didn't see anywhere how I could have a macro that instead of
> replacing the macro with lisp code, calls an external
Josh writes:
> Thanks! This is very helpful.
>
> I have a related question. How can I run an external program right
> before Export that takes as input the current buffer and prints out to
> stdout an updated version of the org file that then is exported?
> Basically I want to pipe the org file
Thanks! This is very helpful.
I have a related question. How can I run an external program right before
Export that takes as input the current buffer and prints out to stdout an
updated version of the org file that then is exported? Basically I want to
pipe the org file through a filter that
On Sunday, 10 Mar 2019 at 15:37, Josh wrote:
> Hi,
>
> I am new to emacs and orgmode. I spent the last couple days reading most
> of the docs before diving in, but I didn't see anywhere how I could have a
> macro that instead of replacing the macro with lisp code, calls an
> external program
Hi,
I am new to emacs and orgmode. I spent the last couple days reading most
of the docs before diving in, but I didn't see anywhere how I could have a
macro that instead of replacing the macro with lisp code, calls an
external program instead.
Something like:
#+MACRO: func call
