From: Greg Minshall <firstname.lastname@example.org>
Date: Tue, 23 Feb 2021 17:24:33 +0300 [thread overview]
Message-ID: <email@example.com> (raw)
i have a question about org-in-org source blocks. i volunteered to help
in an effort to provide a tutorial of using the ESS (Emacs Speaks
Statistics) package for R, in particular, from org mode.
i'd like to write my contribution as a .org file. i'd like to include
fragments of org code, including source blocks (in R). and, i'd like to
show various result types. so, i'd like to be able to have the
#+RESULTS show up in the org-in-org source block as exported inside the
containing .org file.
and, i'd like to trigger all this from a makefile, using some emacs
batch script to export the containing .org file into a .html or .pdf
(i *think*) what i would like to end up with is what it would like if i
had manually opened the org-in-org source blocks (C-c'), then went to
each (or, possibly, selected, i guess) source blocks inside *that*
(org-in-org) source block, and executed each, producing a #+RESULTS
block for each, then closed the org-in-org source block (C-c', again),
and then exported the containing .org file.
is this possible? any ideas?
next reply other threads:[~2021-02-23 14:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-23 14:24 Greg Minshall [this message]
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 ` org-in-org Berry, Charles via General discussions about Org-mode.
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
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
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).