emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Thomas S. Dye" <tsd@tsdye.com>
To: Andreas Leha <andreas.leha@med.uni-goettingen.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: source code block export no expansion
Date: Tue, 7 Dec 2010 08:37:19 -1000	[thread overview]
Message-ID: <2062CE38-02AE-48AE-A36E-92605E973FCB@tsdye.com> (raw)
In-Reply-To: <4CFE7126.8090304@med.uni-goettingen.de>

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: mod1
>  #+begin_src R :tangle no :export code
>    print("mod1")
>  #+end_src
>
>  #+srcname: mod2
>  #+begin_src R :tangle no :export code
>    print("mod2")
>  #+end_src
>
>  #+srcname: part1
>  #+begin_src R :noweb yes :tangle yes :export code :session *R*
>    <<mod1>>
>    <<mod2>>
>  #+end_src
>
>
> Now during the tangling I would like to tangle just the full part1 -
> with noweb links being expanded.  Also during execution the noweb  
> links
> should be expanded.  This is not a problem.
>
> But at the same time, during the export I'd like to export all three
> code snippets, but I'd prefer the noweb links not to be expanded.  Is
> that possible?
>
> Thanks in advance,
> Andreas
>
> _______________________________________________
> Emacs-orgmode mailing list
> Please use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode

  reply	other threads:[~2010-12-07 18:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-07 17:38 source code block export no expansion Andreas Leha
2010-12-07 18:37 ` Thomas S. Dye [this message]
2010-12-07 18:49   ` Andreas Leha
2010-12-07 19:33     ` Thomas S. Dye
2010-12-07 19:46       ` Andreas Leha
2010-12-07 20:14         ` Thomas S. Dye
2010-12-08  6:55           ` Andreas Leha
2010-12-08 16:49             ` Thomas S. Dye

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=2062CE38-02AE-48AE-A36E-92605E973FCB@tsdye.com \
    --to=tsd@tsdye.com \
    --cc=andreas.leha@med.uni-goettingen.de \
    --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).