emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Yu <yu_icq@gmx.at>
To: Paul Magwene <pmmagic@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Weirdness re: inclusion of figures
Date: Thu, 16 Feb 2012 13:59:20 +0100	[thread overview]
Message-ID: <CANtbJLEZX5e00UFCykdMJ668yeovmeQ7VHGxA-qAHda2Y-j6vA@mail.gmail.com> (raw)
In-Reply-To: <CABoaWcW4gsBt60sezCWMakKhag+p9OEb_uU4Soz4-Ug1ryBROw@mail.gmail.com>

Hello!

The behaviour is actually as expected. To understand this, you have to
consider, that org-mode currently only seems to recognize the relation
between source block and #+result paragraph if one of these two
conditions holds:
  o The "#+result:" line follows the source code without any text in between.
  o Both code block and "#+result:" line are labeled with the same name.

Also consider, as said by Nick Dokos, the significance of the
":exports" header argument:
  o By default the result is computed but not exported.
  o If the (unnamed) result is delimited from the source code by
intervening text, it is no longer considered any source blocks result:
The exporter just ignores the "#+result:" line and includes the image
into the exported file.

Labelling a source code block can be done with a "#+NAME:" line
preceding the code block. When evaluating the code block, the
"#+results"-line automatically gets named too. When reevaluating a
code block then the contents of this "#+results" entry is correctly
refreshed even after intervening code.

What you want thus probably is:

  : #+name: code-block
  : #+begin_src R :file z.png :results output graphics
  : plot(matrix(rnorm(100), ncol=2), type="l")
  : #+end_src
  :
  : Intervening text
  :
  : #+results: code-block
  : [[file:z.png]]

I did some tests to verify I'm right about this though, having
installed a recent version from git (at most 2 days since the last
pull):
  o No intervening text, no ":exports": Image is not exported.
  o No intervening text, ":exports both": Image is exported once; When
exporting the code is rerun.
  o Intevening text, no ":exports": The image is exported once. The
code block is not rerun on export.
  o Intervening text, ":exports both": The code is run twice (!), the
image is exported both before and after the text.

king regards, Yu


2012/2/16 Paul Magwene <pmmagic@gmail.com>:
> Hi All,
>
> I'm trying to get up to speed with org-mode and babel for doing
> reproducible computational research.  I'm just starting to play around
> with simple examples, and I'm baffled by the following.
>
> This first example, when exported to HTML or LaTeX produces the
> expected result -- a simply code block with one embedded figure.
>
> # Example 1.
>
> This is my R example:
>
> #+begin_src R :file z.png :results output graphics
> plot(matrix(rnorm(100), ncol=2), type="l")
> #+end_src
>
> Some intervening text...
>
> #+results:
> [[file:z.png]]
>
>
> However, this almost identical example, minus the intervening text
> between the code and the results, doesn't include the figure:
>
> # Example 2
>
> This is my R example:
>
> #+begin_src R :file z.png :results output graphics
> plot(matrix(rnorm(100), ncol=2), type="l")
> #+end_src
>
> #+results:
> [[file:z.png]]
>
>
> What gives here? Do I always need to have intervening text between the
> source code and results in order to get a figure in the exported
> document?
>
> Thanks,
> Paul
>

      parent reply	other threads:[~2012-02-16 13:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-16  3:42 Weirdness re: inclusion of figures Paul Magwene
2012-02-16  3:45 ` Paul
2012-02-16  4:44 ` Nick Dokos
2012-02-16 12:59 ` Yu [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=CANtbJLEZX5e00UFCykdMJ668yeovmeQ7VHGxA-qAHda2Y-j6vA@mail.gmail.com \
    --to=yu_icq@gmx.at \
    --cc=emacs-orgmode@gnu.org \
    --cc=pmmagic@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).