emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Eric Schulte <schulte.eric@gmail.com>
To: Mark Cox <markcox80@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: No Expansion of noweb references when exporting
Date: Thu, 19 May 2011 07:50:39 -0600	[thread overview]
Message-ID: <878vu2iyt3.fsf@gmail.com> (raw)
In-Reply-To: BANLkTik9dbr4ecq4-TAManY-y9aN7bUKyw@mail.gmail.com

Hi Mark,

Thanks for pointing this out.  After checking the manual [1] for the
noweb header argument I realized you were right, we're not currently
living up to the described behavior.

I've just pushed up a patch which correctly implements the ":noweb yes"
expansion on export behavior.

Best -- Eric

Mark Cox <markcox80@gmail.com> writes:

> Hi,
>
> Is it possible for the output of the expansion of a code block to
> appear in the exported document?
>
> Consider the example:
>
> #+TITLE: No expansion of noweb references when exporting
>
> * Example
> :PROPERTIES:
> :tangle: illustration.hpp
> :END:
> #+srcname: boiler-plate-code-generator()
> #+begin_src emacs-lisp :results output :exports none :tangle no
> (dolist (type '("int8_t" "uint8_t" "float" "double"))
>   (princ (format "template <> %s boiler_plate_code<%s>();\n" type type)))
> #+end_src
> #+begin_src c++ :noweb yes
> <<boiler-plate-code-generator()>>
> #+end_src
>
> When I export this to HTML using C-c C-e b, the text
> <<boiler-plate-code-generator()>> is present. What I would like to see
> is the output that is generated when tangling.
>
> Thanks
> Mark
>


Footnotes: 
[1]  http://orgmode.org/manual/noweb.html

-- 
Eric Schulte
http://cs.unm.edu/~eschulte/

      reply	other threads:[~2011-05-19 14:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-19  4:35 No Expansion of noweb references when exporting Mark Cox
2011-05-19 13:50 ` Eric Schulte [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=878vu2iyt3.fsf@gmail.com \
    --to=schulte.eric@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=markcox80@gmail.com \
    /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).