[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: org-in-org
From: |
Berry, Charles |
Subject: |
Re: org-in-org |
Date: |
Mon, 8 Mar 2021 20:33:59 +0000 |
Greg,
> On Mar 7, 2021, at 11:44 PM, Greg Minshall <minshall@umich.edu> wrote:
>
> i guess when i used the term "recursive execute function" (i tend to
> confuse "execute" and "export"), i was thinking of something like: when
> i export an org file, and it runs into an org-in-org block to export,
> then your code runs on that block. the recursive part is that, when
> your code is runninng on the org-in-org block, and runs into an
> "org-in-org-in-org" block (that is also marked to export), it runs on
> *that*. ad, but not normally infinitum.
I admit to being baffled by this.
If you have nested org src blocks and you recursively enter each org block
using `org-edit-special' and execute the src blocks other than org lang, then
exit with `org-edit-src-exit', when you complete this the org buffer will have
nested src blocks and results with one or more comma escapes prepended to lines
that start with `#+` or `*`.
When you export this, you end up with a document that has the comma escapes
reduced by one in those nested blocks. The appearance of these is not
altogether pleasing to my eye.
Have you tried creating a document with nested org src blocks and stepping
through the recursion to be sure it is something you want and really need?
If you have a particular use case, maybe it can be handled in a one-off manner.
Best,
Chuck