From mboxrd@z Thu Jan  1 00:00:00 1970
From: Eric Schulte <schulte.eric@gmail.com>
Subject: Re: [Babel][Bug] Inconsistent output from babel function	depending
 on how called
Date: Fri, 27 May 2011 10:35:14 -0600
Message-ID: <8739k06r0d.fsf@gmail.com>
References: <BANLkTi=H9tasSwrPy6+JkSjeUz-J_DJtgw@mail.gmail.com>
	<87wrhdqozg.fsf@gmail.com> <4DDEA75B.4040601@christianmoe.com>
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 ([140.186.70.92]:47749)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <schulte.eric@gmail.com>) id 1QQ00Q-0006vK-8K
	for emacs-orgmode@gnu.org; Fri, 27 May 2011 12:35:27 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <schulte.eric@gmail.com>) id 1QQ00P-0003Z7-4Q
	for emacs-orgmode@gnu.org; Fri, 27 May 2011 12:35:22 -0400
Received: from mail-pw0-f41.google.com ([209.85.160.41]:39821)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <schulte.eric@gmail.com>) id 1QQ00O-0003Yl-Vw
	for emacs-orgmode@gnu.org; Fri, 27 May 2011 12:35:21 -0400
Received: by pwi12 with SMTP id 12so1075150pwi.0
	for <emacs-orgmode@gnu.org>; Fri, 27 May 2011 09:35:20 -0700 (PDT)
In-Reply-To: <4DDEA75B.4040601@christianmoe.com> (Christian Moe's message of
	"Thu, 26 May 2011 21:17:47 +0200")
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: </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: mail@christianmoe.com
Cc: Ethan Ligon <ligon@are.berkeley.edu>, "Emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>

Christian Moe <mail@christianmoe.com> writes:

>> No, this is expected (if possibly under-documented behavior).  The
>> :results header arguments are associated with the code block and *not*
>> with the #+call line.  To get the desired behavior, you must specify the
>> :results header argument on the #+call: line thusly.
>>
>> #+call: print_list(lst=list1) :results output org
>>
>> Best -- Eric
>
> Hi,
>
> I recently made the same mistake, and it took me a while to figure
> things out. I had assumed #+CALLs inherited all the header arguments
> from the code blocks they referenced.
>
> Regarding documentation, I see now that the correct behavior is at
> least implicitly documented in the first example at
> [[info:org#Header%20arguments%20in%20function%20calls]].
>
> It might rate an explicit explanation at
> [[info:org#Evaluating%20code%20blocks]] as well, though.
>
> Yours,
> Christian

I've just updated the documentation at the following to reflect the full
range of #+call line header argument options.

#+begin_src emacs-lisp
  (info "(org)Evaluating code blocks")
#+end_src

Thanks for the recommendation -- Eric

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