From mboxrd@z Thu Jan  1 00:00:00 1970
From: Eric Schulte <eric.schulte@gmx.com>
Subject: Re: [babel] Call lines with "their own" results
Date: Mon, 26 Mar 2012 06:57:45 -0400
Message-ID: <87pqbzr2mt.fsf@gmx.com>
References: <8762dxqbzi.fsf@med.uni-goettingen.de>
Mime-Version: 1.0
Content-Type: text/plain
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([208.118.235.92]:60079)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <eric.schulte@gmx.com>) id 1SCAW9-000744-2M
	for emacs-orgmode@gnu.org; Mon, 26 Mar 2012 10:03:33 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <eric.schulte@gmx.com>) id 1SCAW0-000122-N5
	for emacs-orgmode@gnu.org; Mon, 26 Mar 2012 10:03:28 -0400
Received: from mailout-us.gmx.com ([74.208.5.67]:53012)
	by eggs.gnu.org with smtp (Exim 4.71)
	(envelope-from <eric.schulte@gmx.com>) id 1SCAW0-00011k-GG
	for emacs-orgmode@gnu.org; Mon, 26 Mar 2012 10:03:20 -0400
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/emacs-orgmode>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=subscribe>
Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
To: Andreas Leha <andreas.leha@med.uni-goettingen.de>
Cc: emacs-orgmode@gnu.org

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/