Jambu> I think there is a strong case for making headlines act as babel
Jambu> srcnames with their body providing content for noweb expansion
Jambu> [3]. This behaviour could be controlled by a buffer local
Jambu> variable.

Eric> This is an interesting suggestion.  Next time I have time I will
Eric> but together a trail implementation to see how naturally this fits
Eric> into the rest of the Babel system.  There could be issues
Eric> (e.g. how to do set header arguments for the headline).

Good to hear this.

I am attaching a mail that I had (accidentally) unicast to Sebastien
elaborating on the possibilities. This could be of interest to the list.

Jambu> If babel supports headlines as srcnames, without requiring additional
Jambu> begin/end directives one could just write,
Jambu>
Jambu> * org-list
Jambu>   - one
Jambu>   - two
Jambu>   - three
Jambu>
Jambu> #+begin_src emacs-lisp :tangle yes :noweb yes
Jambu>   "
Jambu>   <<org-list(:fmt latex)>>
Jambu>   "
Jambu> #+end_src
Jambu>
Jambu> and achieve similar results.
Jambu>

Eric> Yes, however the syntax you've used above to pass a header
Eric> argument to the org-lisp code block violates the existing noweb
Eric> syntax.  The place where you've inserted ":fmt latex" is reserved
Eric> for passing regular arguments to code blocks.

That is precisely my point. 

If org headlines are srcnames there is every reason that they take
arguments. See my attached mail that talks of implicit 'this' and ':fmt'
parameters.

I am not as concerned about the existing syntax, as the possibilities
that could potentially unfold with this mind-twister.

Eric> There has been discussion of allowing post-processing forms for
Eric> code blocks which would take the results of a code block as an
Eric> argument every time the code block has been called and whose
Eric> results would replace the actual code block results, however this
Eric> has not yet been implemented.

If headlines are considered as code blocks one actually inflate
headlines and execute them for interesting side-effects. The attached
mail elaborates on this point.

Thanks,
Jambunathan K.

Attachment: