[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [O] Noweb blocks duplicate during Org export if part of #+include
From: |
Kaushal Modi |
Subject: |
Re: [O] Noweb blocks duplicate during Org export if part of #+include |
Date: |
Wed, 12 Dec 2018 13:50:23 -0500 |
On Sat, Dec 8, 2018 at 4:42 AM Nicolas Goaziou <address@hidden> wrote:
> Now, onto the second case. When evaluating Babel code, the whole initial
> buffer is taken as reference. It allows, for example, to define source
> blocks in a dedicated section, and export another one that calls them.
> When the INCLUDE keyword is expanded, there are two ":noweb-ref
> some_snippet". Even if they are outside the exported subtree, they are
> still concatenated and used as a replacement for "<<some_snippet>".
>
> In a nutshell, that can be surprising, but this is to be expected.
Thank you for the detailed answer.
As I don't know how to "fix" this, I will just remember to not use
Noweb in subtrees that I plan to #+include.