From: Eric Schulte <eric.schulte@gmx.com>
To: Andreas Leha <andreas.leha@med.uni-goettingen.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: [babel] Call lines with "their own" results
Date: Mon, 26 Mar 2012 06:57:45 -0400 [thread overview]
Message-ID: <87pqbzr2mt.fsf@gmx.com> (raw)
In-Reply-To: 8762dxqbzi.fsf@med.uni-goettingen.de
Hi Andreas,
Currently call the behavior you mention below, in which call line
results are named by their arguments and are not unique, is the
implemented behavior. I agree that it would be preferable to switch to
a system in which each call line was given it's own results, however I
am not able to make this change right now (although it is on my TODO
list).
I think for now a workaround like the one you suggest below (or maybe
using an "id" header argument) is probably your best bet.
Best,
Andreas Leha <andreas.leha@med.uni-goettingen.de> writes:
> Hi all,
>
> Is there a way to force #+call line to have their own results block?
> Or what is the best practice to achieve that?
> I remember that there was a thread on this recently...
>
> Example:
> #+name: sampleblock
> #+begin_src R :colnames yes
> data.frame(par=1, val=1)
> #+end_src
>
> I can call this block:
> #+call: sampleblock()
>
> #+results: sampleblock()
> | 1 | 1 |
>
> Now, I want to call this block with different arguments, but instead
> of placing the results here, the result block above gets updated.
> #+call: sampleblock() :colnames yes
>
>
>
> Note: I can cheat to achieve this, but is this the best way?
> #+call: sampleblock(execute="!") :colnames yes
>
> #+results: sampleblock(execute="!")
> | par | val |
> |-----+-----|
> | 1 | 1 |
>
>
>
--
Eric Schulte
http://cs.unm.edu/~eschulte/
prev parent reply other threads:[~2012-03-26 14:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-22 8:24 [babel] Call lines with "their own" results Andreas Leha
2012-03-26 10:57 ` Eric Schulte [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=87pqbzr2mt.fsf@gmx.com \
--to=eric.schulte@gmx.com \
--cc=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).