emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Eric Schulte" <schulte.eric@gmail.com>
To: andrea Crotti <andrea.crotti.0@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Re: Exporting after executing code
Date: Sat, 12 Sep 2009 12:20:20 -0600	[thread overview]
Message-ID: <m2skeshvob.fsf@gmail.com> (raw)
In-Reply-To: <loom.20090912T193643-812@post.gmane.org> (andrea Crotti's message of "Sat, 12 Sep 2009 17:38:35 +0000 (UTC)")

andrea Crotti <andrea.crotti.0@gmail.com> writes:

> Carsten Dominik <carsten.dominik <at> gmail.com> writes:
>
>> 
>> or, for a lighter solution
>> 
>> http://repo.or.cz/w/org-mode.git?a=blob_plain;f=contrib/lisp/org-eval.el;hb=HEAD
>> 
>> or
>> 
>> http://orgmode.org/worg/org-contrib/org-eval-light.php
>> 
>> But org-babel may really be the way to go.
>> 
>> - Carsten
>>
>
> org-babel is really nice I think, there's only one thing I don't understand yet.
> If I want in the same file to have the source code and the output of the 
> source code how should I do??
>
> Once I enable org-babel it executes everything before exporting??
> No finer settings possible?
>
Hi,

There are four export setting using Org-babel.

- none :: neither the code or the results are exported and the block is
          not run
- code :: the fortified code is exported and the block is not run
- results :: the block is run, and the results are exported
- both :: the block is run and both the code and results are exported

These setting are controlled via the :exports header argument, so for
example in the following code block only the code would be included on
export.

#+begin_src ditaa :file test.png :exports code
   +----------------------+
   |                      |
   |                      |
   |          +-----------+
   |          |           |
   |          |           |
   |          |           |
   |          +-----------+
   |                      |
   +----------------------+
#+end_src

If you grab the latest Org-babel code from
http://github.com/eschulte/org-babel/tree/master then you can set the
exports header argument for an entire subtree by setting the subtree's
"exports" property, for example

** show all
   :PROPERTIES:
   :exports:  both
   :END:

Best -- Eric

>
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Remember: use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode

  reply	other threads:[~2009-09-12 18:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-11 12:41 Exporting after executing code andrea Crotti
2009-09-11 13:48 ` Detlef Steuer
2009-09-11 15:04   ` andrea Crotti
2009-09-11 15:53     ` Nick Dokos
2009-09-11 16:54       ` andrea Crotti
2009-09-11 17:57         ` Sebastian Rose
2009-09-11 20:34           ` Carsten Dominik
2009-09-12 17:38             ` andrea Crotti
2009-09-12 18:20               ` Eric Schulte [this message]
2009-09-14 13:27                 ` andrea Crotti

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=m2skeshvob.fsf@gmail.com \
    --to=schulte.eric@gmail.com \
    --cc=andrea.crotti.0@gmail.com \
    --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).