Re: [O] [Babel][Bug] Inconsistent output from babel function depending on how called

2011-05-27 Thread Eric Schulte
Christian Moe 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.

Re: [O] [Babel][Bug] Inconsistent output from babel function depending on how called

2011-05-27 Thread Eric Schulte
Ethan Ligon writes: > So, the ":result output org" ought to be associated with the *call*, > not with the function. That makes good sense. But perhaps it still > doesn't work quite as it ought... > > On Thu, May 26, 2011 at 11:46 AM, Eric Schulte wrote: >> Ethan Ligon writes: >> >>> I'd like

Re: [O] [Babel][Bug] Inconsistent output from babel function depending on how called

2011-05-27 Thread Eric Schulte
Ethan Ligon writes: > On Thu, May 26, 2011 at 12:17 PM, Christian Moe wrote: >>> 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

Re: [O] [Babel][Bug] Inconsistent output from babel function depending on how called

2011-05-26 Thread Ethan Ligon
On Thu, May 26, 2011 at 12:17 PM, Christian Moe wrote: >> 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 argu

Re: [O] [Babel][Bug] Inconsistent output from babel function depending on how called

2011-05-26 Thread Ethan Ligon
So, the ":result output org" ought to be associated with the *call*, not with the function. That makes good sense. But perhaps it still doesn't work quite as it ought... On Thu, May 26, 2011 at 11:46 AM, Eric Schulte wrote: > Ethan Ligon writes: > >> I'd like to call a simple babel code block

Re: [O] [Babel][Bug] Inconsistent output from babel function depending on how called

2011-05-26 Thread Christian Moe
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) :

Re: [O] [Babel][Bug] Inconsistent output from babel function depending on how called

2011-05-26 Thread Eric Schulte
Ethan Ligon writes: > 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 heading

[O] [Babel][Bug] Inconsistent output from babel function depending on how called

2011-05-26 Thread Ethan Ligon
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". #+so