Ethan Ligon li...@are.berkeley.edu writes:
On Thu, May 26, 2011 at 12:17 PM, Christian Moe m...@christianmoe.com 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
Ethan Ligon li...@are.berkeley.edu 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 schulte.e...@gmail.com wrote:
Christian Moe m...@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
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.
Ethan Ligon li...@are.berkeley.edu 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
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)
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 schulte.e...@gmail.com wrote:
Ethan Ligon li...@are.berkeley.edu writes:
I'd
On Thu, May 26, 2011 at 12:17 PM, Christian Moe m...@christianmoe.com 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
