From: Kaushal Modi <kaushal.modi@gmail.com>
To: emacs-org list <emacs-orgmode@gnu.org>
Subject: Re: Noweb blocks duplicate during Org export if part of #+include
Date: Wed, 12 Dec 2018 13:50:23 -0500 [thread overview]
Message-ID: <CAFyQvY3dGVi3KN5_-n+DHTDM2X1uSexRQrMes2z1sw=2VDV00w@mail.gmail.com> (raw)
In-Reply-To: <87wookfj82.fsf@nicolasgoaziou.fr>
On Sat, Dec 8, 2018 at 4:42 AM Nicolas Goaziou <mail@nicolasgoaziou.fr> 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.
prev parent reply other threads:[~2018-12-12 18:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-06 14:34 Noweb blocks duplicate during Org export if part of #+include Kaushal Modi
2018-12-08 9:42 ` Nicolas Goaziou
2018-12-12 18:50 ` Kaushal Modi [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAFyQvY3dGVi3KN5_-n+DHTDM2X1uSexRQrMes2z1sw=2VDV00w@mail.gmail.com' \
--to=kaushal.modi@gmail.com \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).