Hi Mark, Thanks for pointing this out. After checking the manual [1] for the noweb header argument I realized you were right, we're not currently living up to the described behavior.
I've just pushed up a patch which correctly implements the ":noweb yes" expansion on export behavior. Best -- Eric Mark Cox <markco...@gmail.com> writes: > Hi, > > Is it possible for the output of the expansion of a code block to > appear in the exported document? > > Consider the example: > > #+TITLE: No expansion of noweb references when exporting > > * Example > :PROPERTIES: > :tangle: illustration.hpp > :END: > #+srcname: boiler-plate-code-generator() > #+begin_src emacs-lisp :results output :exports none :tangle no > (dolist (type '("int8_t" "uint8_t" "float" "double")) > (princ (format "template <> %s boiler_plate_code<%s>();\n" type type))) > #+end_src > #+begin_src c++ :noweb yes > <<boiler-plate-code-generator()>> > #+end_src > > When I export this to HTML using C-c C-e b, the text > <<boiler-plate-code-generator()>> is present. What I would like to see > is the output that is generated when tangling. > > Thanks > Mark > Footnotes: [1] http://orgmode.org/manual/noweb.html -- Eric Schulte http://cs.unm.edu/~eschulte/