From: "Eric Schulte" <schulte.eric@gmail.com>
To: Nathan Neff <nathan.neff@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: [org-babel] Dynamic Tangle?
Date: Mon, 13 Dec 2010 13:58:39 -0700 [thread overview]
Message-ID: <871v5lgzk0.fsf@gmail.com> (raw)
In-Reply-To: <AANLkTin_QDLQwPJi9xhY8+U7nz56Og7wCiVhtF+5gtpw@mail.gmail.com> (Nathan Neff's message of "Mon, 6 Dec 2010 22:57:58 -0600")
Hi Nathan,
The easiest way I can think of to accomplish templates would be through
some abuse of code block evaluation. Maybe something like the following
would work...
** tangle templates
#+source: template-heading
#+begin_src emacs-lisp
some stuff here
#+end_src
#+source: template-footing
#+begin_src emacs-lisp
some other stuff here
#+end_src
#+source: template
#+begin_src sh :results output :noweb yes :var body="body stuff"
heading=$(cat<<EOF
<<template-heading>>
EOF
)
footing=$(cat<<EOF
<<template-footing>>
EOF
)
echo $heading
echo "$body"
echo $footing
#+end_src
#+call: template[:noweb yes](body="something new")
#+results: template[:noweb yes](body="something new")
: some stuff here
: something new
: some other stuff here
I hope this makes sense, and isn't too gross looking, for a really clean
implementation the template function could be located in a different org
file using the library of babel.
Note, that this relies upon an improvement to variable escaping that I
just pushed up to the latest version in git.
Best -- Eric
Nathan Neff <nathan.neff@gmail.com> writes:
> I'm preparing a presentation and I'm getting using tangle to show code /and/
> produce working code examples -- this is really cool.
>
> It is possible to define a "template" and pass code blocks to it?
> For example: (Using pseudo-org-babel-code for brevity)
>
> #+template
> header code
> <<code_that_is_passed_to_me>>
> footer code
>
> #+example1 :render #+template with 1111111
> 1111111111
>
> #+example2 :render #+template with 222222
> 222222222
>
> The tangled output would be:
>
> header code
> 11111111111
> footer code
>
> header code
> 2222222222
> footer code
>
> I'm already able to use org-babel like below, but I have to
> put a <<footer>> and a <<header>> in each code block.
>
> Here's my existing setup:
> #+header
> header code
>
> #+footer
> footer code
>
> #+example1
> <<header>> <-- I have to specify these <<header>> and <<footer>> in
> each code block
> 11111111111
> <<footer>>
>
> #+example2
> <<header>>
> 2222222222
> <<footer>>
>
> Thanks again for org-babel -- I'll post my presentation when I get it done.
>
> --Nate
>
> _______________________________________________
> 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
prev parent reply other threads:[~2010-12-13 20:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-07 4:57 [org-babel] Dynamic Tangle? Nathan Neff
2010-12-13 20:58 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871v5lgzk0.fsf@gmail.com \
--to=schulte.eric@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=nathan.neff@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.