From mboxrd@z Thu Jan  1 00:00:00 1970
From: Eric Schulte <schulte.eric@gmail.com>
Subject: Re: evaluation context in call statements
Date: Sun, 30 Jun 2013 16:24:54 -0600
Message-ID: <87mwq7kv0r.fsf@gmail.com>
References: <444ea6cff489e2adc97092bdac881aef@mail.rickster.com>
	<878v1y574d.fsf@Rainer.invalid> <874ncm55ma.fsf@Rainer.invalid>
	<CALn3zohXL0x21gYhKj7QS0prJXDC_OcC4qgcejAqtk7b8-KytQ@mail.gmail.com>
	<87r4fq3ptf.fsf@Rainer.invalid> <87ip11h2zq.fsf@gmail.com>
	<87fvw5fkpt.fsf@Rainer.invalid> <87k3lgewrv.fsf@gmail.com>
	<87bo6sqhir.fsf@Rainer.invalid>
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="=-=-="
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:51043)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <schulte.eric@gmail.com>) id 1UtRai-0006ga-DT
	for emacs-orgmode@gnu.org; Sun, 30 Jun 2013 20:03:37 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <schulte.eric@gmail.com>) id 1UtRah-0001Wa-6b
	for emacs-orgmode@gnu.org; Sun, 30 Jun 2013 20:03:36 -0400
Received: from mail-pb0-x230.google.com ([2607:f8b0:400e:c01::230]:52641)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <schulte.eric@gmail.com>) id 1UtRag-0001WM-Vp
	for emacs-orgmode@gnu.org; Sun, 30 Jun 2013 20:03:35 -0400
Received: by mail-pb0-f48.google.com with SMTP id ma3so4148324pbc.35
	for <emacs-orgmode@gnu.org>; Sun, 30 Jun 2013 17:03:34 -0700 (PDT)
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: Achim Gratz <Stromeko@nexgo.de>
Cc: emacs-orgmode@gnu.org

--=-=-=
Content-Type: text/plain

Achim Gratz <Stromeko@nexgo.de> writes:

> Eric Schulte writes:
>>>> My vote is for adding #+name support to call lines, and then handling
>>>> their results in the same manner as code block results.
>>
>> Achim Gratz <Stromeko@nexgo.de> writes:
>>> I'm not sure what this would entail other than replacing the call with
>>> its arguments with the name of the call in the results line.  But yes,
>>> that'd be a step forward, although you'd have to be careful when copying
>>> calls.
>>>
>>
>> This could work exactly as named source blocks work.  E.g.,
> [...]
>
> I see.  The problem then really is that #+CALL lines are currently
> "implicitly named" by copying their arguments to the results line.  If
> explicit naming is allowed, this implicit naming should go away or at
> least not be the default, IMHO.
>

Exactly.

I've just pushed up a patch which implements this change.  Call lines
should now work exactly as named code blocks providing clarity,
uniformity and the flexibility to run multiple identical call lines.


--=-=-=
Content-Type: text/x-org
Content-Disposition: inline; filename=named-call.org

#+name: bar
#+BEGIN_SRC emacs-lisp 
:baz
#+END_SRC

#+call: bar()

#+RESULTS:
: :baz

#+call: bar()

#+RESULTS:
: :baz

#+name: foo
#+call: bar()

#+RESULTS: foo
: :baz

#+name: foo2
#+call: bar()

#+RESULTS: foo2
: :baz

#+name: foo
#+call: bar()

--=-=-=
Content-Type: text/plain


Cheers,

-- 
Eric Schulte
http://cs.unm.edu/~eschulte

--=-=-=--