From: Andreas Leha <andreas.leha@med.uni-goettingen.de>
To: emacs-orgmode@gnu.org
Subject: Re: Tangle including code generating graphics for :results graphics
Date: Thu, 24 Sep 2015 09:41:56 +0100 [thread overview]
Message-ID: <olua8scqkdn.fsf@med.uni-goettingen.de> (raw)
In-Reply-To: m2twqkfcj3.fsf@krugs.de
Hi Rainer,
Rainer M Krug <Rainer@krugs.de> writes:
> Hi
>
> Is it possible to tangle an R code block including the code which is
> generating the graphs when using =:results graphics= ?
>
> I would like to tangle these code blocks generating the graphs as I
> would like to have a script which I can use to easily update all graphs
> when the simulated input data is updated. I have this for the actual
> analysis which works perfectly, but would like to have the same for the
> graphs. At the same time, I like the clarity of specifying :width and
> :height and other parameter for the plotting as header arguments.
>
> I have
>
> ,----
> | :PROPERTIES:
> | :header-args+: :prologue "env <- fitBFGS; attach(env)"
> | :header-args+: :epilogue "detach(env); rm(env)"
> | :END:
> `----
>
> and this is tangled perfectly - but obviously not the code for
> plotting. Is there an argument / setting to enable this?
>
> Thanks,
>
> Rainer
That is a very relevant question and I'd be interested in the answer as
well. But I am not aware of any support by Org mode for this.
I guess calling `org-babel-expand-src-block' prior to tangling would
answer your needs?
This would be desirable not only for plotting code blocks, also data
passed to code block is 'lost' during tangling.
I think it would be good to have a source block header argument, say
`:tangleexpanded', controlling such functionality.
WDYT?
Regards,
Andreas
next prev parent reply other threads:[~2015-09-24 8:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-24 8:26 Tangle including code generating graphics for :results graphics Rainer M Krug
2015-09-24 8:41 ` Andreas Leha [this message]
2015-09-24 9:03 ` Rainer M Krug
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=olua8scqkdn.fsf@med.uni-goettingen.de \
--to=andreas.leha@med.uni-goettingen.de \
--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).