From mboxrd@z Thu Jan  1 00:00:00 1970
From: Ethan Ligon <ligon@are.berkeley.edu>
Subject: [Babel][Bug] Inconsistent output from babel function depending on
 how called
Date: Thu, 26 May 2011 11:37:33 -0700
Message-ID: <BANLkTi=H9tasSwrPy6+JkSjeUz-J_DJtgw@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([140.186.70.92]:38029)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <ethan.ligon@gmail.com>) id 1QPfRU-0002Yf-Rz
	for emacs-orgmode@gnu.org; Thu, 26 May 2011 14:37:57 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <ethan.ligon@gmail.com>) id 1QPfRU-0004oJ-0V
	for emacs-orgmode@gnu.org; Thu, 26 May 2011 14:37:56 -0400
Received: from mail-fx0-f41.google.com ([209.85.161.41]:42138)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <ethan.ligon@gmail.com>) id 1QPfRT-0004mO-SL
	for emacs-orgmode@gnu.org; Thu, 26 May 2011 14:37:55 -0400
Received: by fxm18 with SMTP id 18so1048397fxm.0
	for <emacs-orgmode@gnu.org>; Thu, 26 May 2011 11:37:54 -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: </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: "Emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>

I'd like to call a simple babel code block to generate org-code
If I define a list thusly:

#+results: list1
 - foo
 - bar

Then I define a code block thusly, and execute it by C-c C-c on the
"source" line.  That yields the desired result: a sequence of headings
under "#+results: print_list".

#+source: print_list(lst=list1)
#+begin_src sh :results output org
  for i in $lst; do
    echo "* $i"
  done
#+end_src

#+results: print_list
#+BEGIN_ORG
* foo
* bar
#+END_ORG

Now I want to reuse the code block to generate other sequences of
headings.  But even if I call it with the *same* list, instead of the
desired headings, I get a literal, as below.

#+call: print_list(lst=list1)

#+results: print_list(lst=list1)
: * foo
: * bar

I think this qualifies as a bug---surely the method of calling the
code block shouldn't affect the output?

Thoughts, patches, or work-arounds welcomed!

Thanks,
-Ethan

-- 
Ethan Ligon, Associate Professor
Agricultural & Resource Economics
University of California, Berkeley