emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Eric Schulte" <schulte.eric@gmail.com>
To: Eric S Fraga <e.fraga@ucl.ac.uk>
Cc: org-mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: [babel] difference in export output if including file
Date: Tue, 07 Sep 2010 23:52:48 -0600	[thread overview]
Message-ID: <874oe0u6hb.fsf@gmail.com> (raw)
In-Reply-To: <8762yl69nw.wl%ucecesf@ucl.ac.uk> (Eric S. Fraga's message of "Sat, 04 Sep 2010 12:16:35 +0100")

Hi Eric,

I've changed the hook through which code blocks are evaluated so that
this evaluation now takes place after included files have been included.

Hopefully this will fix the issue you mentioned.

Best -- Eric

Eric S Fraga <ucecesf@ucl.ac.uk> writes:

> Hello,
>
> I am using the plantuml babel interface to generate diagrams in a
> document.  If I have the following inline in my main document,
>
> #+CAPTION: Scenario generation and evaluation
> #+LABEL:   fig:scenario-evaluation-cycle
> #+ATTR_LATEX: width=\linewidth
>
> #+srcname: flowchart
> #+begin_src plantuml :file figures/scenario-to-network-and-evaluation.png :exports none
> (*) --> "A node"
> #+end_src
>
> #+results: flowchart
> [[file:figures/scenario-to-network-and-evaluation.png]]
>
> this works fine and only the figure appears in the latex export.  If,
> however, I place this code in another org file and "#+include" that
> file, the export includes the source code as well in the latex export.
>
> Can anybody please suggest how to fix this?  Is this my fault somehow
> or is this a bug in org or babel?
>
> Thanks,
> eric
> -- 
> Eric S Fraga
> GnuPG: 8F5C 279D 3907 E14A 5C29  570D C891 93D8 FFFC F67D

  reply	other threads:[~2010-09-08  5:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-04 11:16 [babel] difference in export output if including file Eric S Fraga
2010-09-08  5:52 ` Eric Schulte [this message]
2010-09-09  5:40   ` Eric S Fraga

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=874oe0u6hb.fsf@gmail.com \
    --to=schulte.eric@gmail.com \
    --cc=e.fraga@ucl.ac.uk \
    --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).