From: "Charles C. Berry" <ccberry@ucsd.edu>
To: Zack Piper <zack@apertron.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: Referring to an Org Babel variable in the invocation arguments to another Org Babel code block
Date: Sun, 1 Jan 2017 10:51:38 -0800 [thread overview]
Message-ID: <alpine.OSX.2.20.1701011009490.1326@charles-berrys-macbook.local> (raw)
In-Reply-To: <7c1389a5-10f5-dd79-5764-137ab48a9013@apertron.net>
On Sun, 1 Jan 2017, Zack Piper wrote:
> Hi Nicolas,
> I tried "c", and it gives me:
>
>>>> c <<<
>
> as the result.
>
> I would like it to use the _variable_ "c", not the literal string.
> So the result should be ">>> test <<<"
>
You mean you want to use the `name' of one `:var name=assign' argument
in the `assign' part of another --- something like what `let*' does in
lisp.
But you simply cannot do that.
`(info "(org) var")' tells us what you can do:
#+BEGIN_QUOTE
The following syntax is used to pass arguments to `src' code blocks
using the `:var' header argument.
:var name=assign
The `assign' is a literal value, such as a string `"string"', a number
`9', a reference to a table, a list, a literal example, another code
block (with or without arguments), or the results from evaluating a
code block.
#+END_QUOTE
The `name' of one argument is none of these (regardless of its effect when
the body of the src block is executed, which BTW depends on the src block
language).
There are other approaches that might serve a purpose in babel src blocks
like that served by `let*' in lisp:
- putting variables in a table (possibly invoking `org-sbe' in a
formula) and then referencing table cells
- writing other src blocks to handle the preliminary processing and
referncing them
- writing an elisp src block that does those preliminaries (perhaps
using `org-babel-ref-resolve' to call other src blocks), then builds
a string specifying a call to your shell src block and calls it
using `org-babel-ref-resolve'.
- using a noweb reference that executes another src block (or blocks).
- setting property values and referencing them
You might have better luck getting guidance on a useful approach by
trying to describe what you want to accomplish.
HTH,
Chuck
prev parent reply other threads:[~2017-01-01 18:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-27 13:02 Referring to an Org Babel variable in the invocation arguments to another Org Babel code block Zack Piper
2016-12-27 17:56 ` Charles C. Berry
2016-12-27 18:17 ` Zack Piper
2016-12-28 23:36 ` Zack Piper
2016-12-29 15:49 ` Nicolas Goaziou
2017-01-01 16:15 ` Zack Piper
2017-01-01 18:51 ` Charles C. Berry [this message]
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=alpine.OSX.2.20.1701011009490.1326@charles-berrys-macbook.local \
--to=ccberry@ucsd.edu \
--cc=emacs-orgmode@gnu.org \
--cc=zack@apertron.net \
/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).