From: suvayu ali <fatkasuvayu+linux@gmail.com>
To: John Hendy <jw.hendy@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Selective export of Babel code blocks
Date: Mon, 18 Jun 2012 19:08:06 +0200 [thread overview]
Message-ID: <CAMXnza1yv3W41OOR1=865JUA+zBQc+Y5ieiSGeHDd=+O+yyF4A@mail.gmail.com> (raw)
In-Reply-To: <CA+M2ft9_a2QFmdOAr8XZN5ic_-wnLHxOjbxLek7NhfSMUts3Ng@mail.gmail.com>
Hi John,
My R knowledge is zero, but I'll give it a shot.
On Mon, Jun 18, 2012 at 6:50 PM, John Hendy <jw.hendy@gmail.com> wrote:
> #+name: preamble
> #+begin_src R :exports none
> tikzDevice("file-name")
> #+end_src
>
Are you trying to use "file-name" as a variable? if so I think the
source block header should include this: ":var file-name" and the source
block can refer to the variable as $file-name.
> And by the org-mode Babel documentation it looks like I can do
> something like:
>
> <<preamble(file-name=file_1.tex)>>
I'm not sure about this. The syntax seems correct but I don't quite
understand the following statement from the manual:
It is possible to include the _results_ of a code block rather than
the body. This is done by appending parenthesis to the code block name
which may optionally contain arguments to the code block as shown
below.
<<code-block-name(optional arguments)>>
My lack of knowledge of R doesn't help either. A little experimentation
should resolve it I think. :)
HTH
--
Suvayu
Open source is the future. It sets us free.
next prev parent reply other threads:[~2012-06-18 17:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-18 14:53 Selective export of Babel code blocks John Hendy
2012-06-18 16:08 ` suvayu ali
2012-06-18 16:50 ` John Hendy
2012-06-18 17:08 ` suvayu ali [this message]
2012-06-18 17:37 ` William LÉCHELLE
2012-06-18 17:11 ` Thomas S. Dye
2012-06-18 17:16 ` suvayu ali
2012-06-18 17:31 ` John Hendy
2012-06-18 18:06 ` Andreas Leha
2012-06-18 19:05 ` Thomas S. Dye
2012-06-19 12:55 ` suvayu ali
2012-06-19 13:36 ` John Hendy
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='CAMXnza1yv3W41OOR1=865JUA+zBQc+Y5ieiSGeHDd=+O+yyF4A@mail.gmail.com' \
--to=fatkasuvayu+linux@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=jw.hendy@gmail.com \
/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).