emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Sebastian Rose <sebastian_rose@gmx.de>
To: andrea Crotti <andrea.crotti.0@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Re: [babel] dot in pdf directly
Date: Tue, 10 Nov 2009 15:40:07 +0100	[thread overview]
Message-ID: <87pr7q4f5k.fsf@gmx.de> (raw)
In-Reply-To: <loom.20091110T071837-637@post.gmane.org> (andrea Crotti's message of "Tue, 10 Nov 2009 06:20:40 +0000 (UTC)")

andrea Crotti <andrea.crotti.0@gmail.com> writes:
> Eric Schulte <schulte.eric <at> gmail.com> writes:
>
>> 
>> The two separate mechanisms are confusion, but for now are necessary to
>> allow org-mode users to evaluate some simple block types (like dot) on
>> export without having to load up all of org-babel.
>> 
>> I hope the above isn't too confusing :) -- Eric
>> 
>
>
> No no thanks a lot not it's very clear.
> Coming back to my original question, am I able to insert directly
> the eps generated in my final generated pdf??
>
> Maybe I have to
> #+begin_dot -Tpdf -o file.pdf
> ...
> #+end_dot
>
> And then somewhere write some latex code to include it?
> #+begin_latex
> \includegraphics..
> #+end_latex

Yes, you can include the eps image like this at any point - not sure if
you need to run the export twice, once the dot block changes.


But the dot block itself will always be executed and replaced by the
resulting image. This is absolutely fine in 99% of all cases.

Suppose you want to refer to the image several times, how about this
then: 

   1. Create a file your-org-directory/images/images.org
   2. Put all images into that file, that you need to reference more
      than once, or that you need to be out of sight to avoid clutter.
   3. Include your images using the relative path to
      ../your-org-directory/images/resulting-image.eps 




Sebastian

  reply	other threads:[~2009-11-10 14:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-09 21:16 [babel] dot in pdf directly andrea Crotti
2009-11-09 22:24 ` Sebastian Rose
2009-11-10  1:13   ` Eric Schulte
2009-11-10  6:20     ` andrea Crotti
2009-11-10 14:40       ` Sebastian Rose [this message]
2009-11-10 15:41         ` Eric Schulte
2009-11-10 17:13           ` andrea Crotti
2009-11-10 19:10             ` Eric Schulte
2009-11-12 18:35               ` andrea Crotti
2009-11-12 18:43                 ` Julien Barnier

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=87pr7q4f5k.fsf@gmx.de \
    --to=sebastian_rose@gmx.de \
    --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).