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 #+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/
