From: John Kitchin <jkitchin@andrew.cmu.edu>
To: Alan Schmitt <alan.schmitt@polytechnique.org>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: tangle on export
Date: Thu, 24 Sep 2015 07:51:53 -0400 [thread overview]
Message-ID: <CAJ51EToQ5Ki3VoKrLhOC=6M7UQQ3WEqJxKJA9j2=hqU__=uAaw@mail.gmail.com> (raw)
In-Reply-To: <m2eghortkp.fsf@charm-ecran.irisa.fr>
[-- Attachment #1: Type: text/plain, Size: 1380 bytes --]
I would add a third Elisp block that calls org-babel-tangle. Assuming all
your code blocks execute on export that will make it tangle. Or I have also
made an Elisp block that does the tangle and then runs the export command.
I.e. Not using the keyboard shortcuts for export.
On Thursday, September 24, 2015, Alan Schmitt <
alan.schmitt@polytechnique.org> wrote:
> Hello,
>
> I have a question I feel is very basic but I did not find the answer in
> the manual. How can I trigger the tangling of a block upon export.
>
> More precisely, I want to give the following example in a lecture:
>
> #+name:hello
> #+begin_src ocaml :tangle myprog.ml
> Printf.printf "Bonjour le monde !\n"
> #+end_src
>
> #+BEGIN_SRC sh :exports both :results verbatim
> ocamlc -o myprog myprog.ml
> ./myprog
> #+END_SRC
>
> where I show a program to be compiled and actually compile it. Is there
> a header I should put on the "hello" block to tangle it when I export
> it?
>
> Thanks,
>
> Alan
>
> --
> OpenPGP Key ID : 040D0A3B4ED2E5C7
> Athmospheric CO₂ (Updated September 22, 2015, Mauna Loa Obs.): 397.77 ppm
>
--
John
-----------------------------------
Professor John Kitchin
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-7803
@johnkitchin
http://kitchingroup.cheme.cmu.edu
[-- Attachment #2: Type: text/html, Size: 1917 bytes --]
prev parent reply other threads:[~2015-09-24 11:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-24 10:37 tangle on export Alan Schmitt
2015-09-24 11:17 ` Rainer M Krug
2015-09-24 12:14 ` Andreas Leha
2015-09-24 13:33 ` Alan Schmitt
2015-09-24 13:43 ` Andreas Leha
2015-09-24 13:36 ` Alan Schmitt
2015-09-24 11:51 ` John Kitchin [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='CAJ51EToQ5Ki3VoKrLhOC=6M7UQQ3WEqJxKJA9j2=hqU__=uAaw@mail.gmail.com' \
--to=jkitchin@andrew.cmu.edu \
--cc=alan.schmitt@polytechnique.org \
--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).