Re: babel/noweb concatenation of equally-named code blocks fails?

[Greg Minshall <minshall@umich.edu>]

Nicolas,

thank you.  wordsmithing opens up endless possibilities, so i don't know
that the following is at all an improvement on your suggestion.  but, it
occurs to me to get the importance of =noweb-ref=, and its role in
concatenation, brought out early on the "page".

one paragraph currently reads:
----
Org can replace the Noweb style reference with the source code---or
concatenation thereof---, or even the results of an evaluation, as
detailed below.  The =noweb= header argument controls expansion of Noweb
syntax references.  Expansions occur when source code blocks are
evaluated, tangled, or exported.
----

an alternative:
----
Depending on the setting of the =noweb= header argument, Org will either
ignore a Noweb style reference, or will attempt to replace it.  In the
latter case, the replacement text will be either the source code from
exactly *one* named source code block (using either a #+name: line, or a
=noweb-ref= header argument), or a concatentation of one or more source
code blocks, each with an identically named =noweb-ref= header argument.
Expansions can only occur when source code blocks are evaluated,
tangled, or exported.  For more details, see below.
----

again, thanks.  cheers, Greg