Re: org-babel-tangle tangles too much !

["Eric Schulte" <schulte.eric@gmail.com>]

Hi Nicolas,

At the moment org-babel believes that any time it sees a valid source
block name surrounded by <<>> characters it is responsible for expanding
them.  Is there a reason that you are abusing this syntax?  It looks as
though you are trying to setup multiple levels of tangling like
org-babel -> noweb -> source.

If you can make a good case for why the behavior you describe should be
supported then we could try to add it behind something like a

#+srcname: b
#+begin_src emacs-lisp :noweb no
  <<a>>
  (b)
#+end_src

header argument, but at first blush the option seems to present too much
opportunity for confusion.  Maybe I'm missing something.

Thanks -- Eric

Nicolas Girard <nicolas.girard@nerim.net> writes:

> Hi,
> I can't get tangle to work the way I want.
> Given a file f.org which contains
>
> =====
> #+srcname: a
> #+begin_src emacs-lisp
> (a)
> #+end_src
>
> #+srcname: b
> #+begin_src emacs-lisp
> <<a>>
> (b)
> #+end_src
> =====
>
> I would like (a) to appear only once in the tangled file f.el.
> All I could get is, that either (a) appears twice (default behaviour),
> or (a) doesn't appear at all when I append ":tangle no" to #+srcname:
> a.
>
> Any thoughts ?