From: "Charles C. Berry" <ccberry@ucsd.edu>
To: Andreas Leha <andreas.leha@med.uni-goettingen.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: export: noweb blocks substituted versus verbatim ?
Date: Sat, 26 Sep 2015 19:54:18 -0700 [thread overview]
Message-ID: <alpine.OSX.2.20.1509261939460.1313@charles-berrys-macbook.local> (raw)
In-Reply-To: <oluio6wpzok.fsf@med.uni-goettingen.de>
On Sat, 26 Sep 2015, Andreas Leha wrote:
> Hi Brian,
>
> Brian Beckman <bc.beckman@gmail.com> writes:
>> Hello -- I have a situation where some code blocks with noweb references in
>> them <<like-this>> are substituted inline when I export the document, and
>> other code blocks with noweb references, are copied verbatim into the
>> exported PDF. I do not know what causes this difference in behavior and I
>> don't know how to control it, but I'd like to control it. I'd like to be
>> able to specify that some blocks have behavior 1 (references substituted
>> inline) and other blocks have behavior 2 (references verbatim).
>>
>> I'm sure this is pilot error, but I'm stumped and would be grateful for advice.
>
> [[ omitted: the MVE ]]
>
> As far as I can see, the difference is that some of the code blocks have
> the header argument `:noweb yes', while others do not.
>
> I do not know how to achieve working noweb extension during evaluation
> but omitting noweb extension during export, though.
>
You can do like this (apart from anonymous backends):
#+header: :noweb (if (org-bound-and-true-p org-export-current-backend) "no" "yes")
HTH,
Chuck
next prev parent reply other threads:[~2015-09-27 2:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-26 21:26 export: noweb blocks substituted versus verbatim ? Brian Beckman
2015-09-26 22:45 ` Andreas Leha
2015-09-26 23:19 ` Brian Beckman
2015-09-27 2:54 ` Charles C. Berry [this message]
2015-09-28 4:40 ` Brian Beckman
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=alpine.OSX.2.20.1509261939460.1313@charles-berrys-macbook.local \
--to=ccberry@ucsd.edu \
--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).