Hi Andreas,
I've put a bug report on Eric and Dan's stack. Thanks again for
pointing this out.
All the best,
Tom
On Dec 7, 2010, at 8:55 PM, Andreas Leha wrote:
Hi Tom,
thanks a lot for looking into it! Fixing this is unfortunately off
my limits.
But for me the unnamed session is a
Hi Tom,
thanks a lot for looking into it! Fixing this is unfortunately off my
limits.
But for me the unnamed session is a valid work-around for me, since I do
not need several sessions right now. Thanks for this hint.
Cheers,
Andreas
Am 07.12.2010 21:14, schrieb Thomas S. Dye:
> Aloha Andre
Aloha Andreas,
Thanks for your patience and persistence. I think this might qualify
as a bug. Using your code, if I don't run R in a session, or if I run
R in a session but don't name the session, everything works as
expected. The behavior changes for me when the session gets a name.
A
Hi Tom,
thanks for the answer and thanks for spotting the typo. But even with
the typo corrected during export the noweb links are still exported.
#+srcname: mod1
#+begin_src R :tangle no :export code
print("mod1")
#+end_src
#+srcname: mod2
#+begin_src R :tangle no :export code
Aloha Andreas,
On Dec 7, 2010, at 8:49 AM, Andreas Leha wrote:
Hi Tom,
thanks for this answer. This indeed comes closer to what I want.
But, some comments:
(1) There seems to be an error in the manual:
In the manual the :noweb tangle header argument is given as :noweb
yes,
which is why I
Hi Tom,
thanks for this answer. This indeed comes closer to what I want.
But, some comments:
(1) There seems to be an error in the manual:
In the manual the :noweb tangle header argument is given as :noweb yes,
which is why I missed that option.
(2) The noweb link are expanded *always* (i.e. e
Aloha Andreas,
Perhaps :noweb tangle will do what you want.
hth,
Tom
On Dec 7, 2010, at 7:38 AM, Andreas Leha wrote:
Hi all,
I have a question about exporting source code blocks. Say, I have
several modules (mod1, mod2), that build a bigger part (part1) of my
program, e.g.:
#+srcname: mo
