emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Berry, Charles" via "General discussions about Org-mode." <emacs-orgmode@gnu.org>
To: Greg Minshall <minshall@umich.edu>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: org-in-org
Date: Mon, 8 Mar 2021 20:33:59 +0000	[thread overview]
Message-ID: <5A355522-851A-4ABD-9807-8CB1D7BE64E7@health.ucsd.edu> (raw)
In-Reply-To: <1841540.1615189497@apollo2.minshall.org>

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


  reply	other threads:[~2021-03-08 20:35 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-23 14:24 org-in-org Greg Minshall
2021-02-23 19:46 ` org-in-org Berry, Charles via General discussions about Org-mode.
2021-03-07 16:14   ` org-in-org Greg Minshall
2021-03-07 22:26     ` org-in-org Berry, Charles via General discussions about Org-mode.
2021-03-08  7:44       ` org-in-org Greg Minshall
2021-03-08 20:33         ` Berry, Charles via General discussions about Org-mode. [this message]
2021-03-09  3:37           ` org-in-org Greg Minshall
2021-02-23 20:30 ` org-in-org Erik Iverson
2021-03-07 15:46   ` org-in-org Greg Minshall
2021-02-23 21:38 ` org-in-org Jeremie Juste
2021-03-07 16:06   ` org-in-org Greg Minshall

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5A355522-851A-4ABD-9807-8CB1D7BE64E7@health.ucsd.edu \
    --to=emacs-orgmode@gnu.org \
    --cc=ccberry@health.ucsd.edu \
    --cc=minshall@umich.edu \
    --subject='Re: org-in-org' \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Code repositories for project(s) associated with this inbox:

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).