From: cberry@tajo.ucsd.edu
To: emacs-orgmode@gnu.org
Subject: Selectively export RESULTS
Date: Tue, 28 Feb 2012 21:04:47 -0800 [thread overview]
Message-ID: <87ty2aw7ps.fsf@tajo.ucsd.edu> (raw)
I sometimes create large documents with many dozens of src blocks and
associated #+RESULTS.
I'd like to be able to grab some of these results blocks and export them
into a document. Since revisions of the src blocks can change the
results, I do not want to just and to copy and paste the results in case
I need to revise the sub-document(s).
And with long running blocks, I do not want to use a noweb strategy to
rerun the code in the src blocks.
As an example, I might have this in a file with many other headlines
and src blocks:
,----
| * Selectively Export Some Results
| :PROPERTIES:
| :EXPORT_FILE_NAME: Selected_Results.pdf
| :EXPORT_TITLE: Selected Results
| :END:
|
| Here are the results from block named "Ablock":
|
| #+CALL: show-results("Ablock")
|
| and here they are for a block named "Bblock":
|
| #+CALL: show-results("Bblock")
`----
and if I put point on the headline and type C-c @ C-c C-e d, I'd like
to have a document that includes the two results blocks in it after each CALL line.
It looks like many of the pieces I need are available, but I don't see
how to stitch them together to create the show-results() function.
TIA,
Chuck
--
Charles C. Berry Dept of Family/Preventive Medicine
cberry at ucsd edu UC San Diego
http://famprevmed.ucsd.edu/faculty/cberry/ La Jolla, San Diego 92093-0901
next reply other threads:[~2012-02-29 5:05 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-29 5:04 cberry [this message]
2012-02-29 7:05 ` Selectively export RESULTS Thomas S. Dye
2012-02-29 16:50 ` cberry
2012-02-29 17:06 ` Eric Schulte
2012-02-29 20:24 ` cberry
2012-03-02 17:24 ` Matthew Landis
2012-03-02 17:48 ` Eric Schulte
2012-03-02 18:33 ` Matthew Landis
2012-03-02 19:33 ` Eric Schulte
2012-03-02 20:12 ` Matthew Landis
2012-03-02 20:20 ` Eric Schulte
2012-03-03 10:43 ` Sebastien Vauban
2012-03-03 14:52 ` Achim Gratz
2012-03-03 23:01 ` Sebastien Vauban
2012-03-04 10:37 ` Achim Gratz
2012-03-04 20:44 ` Sebastien Vauban
2012-03-02 19:42 ` cberry
2012-03-02 20:26 ` Eric Schulte
2012-03-02 21:08 ` cberry
2012-03-02 21:26 ` Nick Dokos
2012-03-02 21:35 ` cberry
2012-03-02 23:01 ` Nick Dokos
2012-03-02 17:59 ` Christophe Pouzat
2012-03-02 18:53 ` Matthew Landis
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=87ty2aw7ps.fsf@tajo.ucsd.edu \
--to=cberry@tajo.ucsd.edu \
--cc=emacs-orgmode@gnu.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
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
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).