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

[Nicolas Goaziou]

Greg Minshall <address@hidden> writes:

> Nicolas, thanks.  i take it this is a change from (recent?) past
> behavior?  

I think this was done between Org 9.1 and 9.2, the final step probably
being 99dbca3d4f2fb30f35309a0bf4c324535b7dc9f3

> it was kind of nice the old way, but i suspect i'll get used
> to the new way (no names, just noweb-ref) fairly soon.

Mixing noweb-ref and names slowed down Noweb expansion very much. We
papered over it using that odd variable:
`org-babel-use-quick-and-dirty-noweb-expansion'. IOW, you had to choose
between speed and accuracy when expanding Noweb blocks.

Now, this is simpler: using NAME keyword is the fast path, with a single
block. Using :noweb-ref is the slow path, but you can concatenate
multiple blocks.