emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: andrea Crotti <andrea.crotti.0@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: [babel] dot in pdf directly
Date: Tue, 10 Nov 2009 17:13:08 +0000 (UTC)	[thread overview]
Message-ID: <loom.20091110T180649-44@post.gmane.org> (raw)
In-Reply-To: m2iqdi2xq1.fsf@gmail.com

Eric Schulte <schulte.eric <at> gmail.com> writes:

> Note that the solution I'm about to propose relies on the use of
> org-babel and #+begin_src dot blocks rather than #+begin_dot blocks.
> 
> When in these situations I will often set the block so that neither the
> code or the resulting image is exported, and so that the results of
> block evaluation are silent.
> 
> #+begin_src dot :file file.pdf :cmdline -Tpdf :exports none :results silent
> ...
> #+end_src
> 
> Then I manually add file links to the image throughout my document.
> 
> [[file:file.pdf]]
> 
> Whenever I change the contents of the block I manually re-evaluate the
> block with C-c C-c and the image to which all of the links point is
> updated.
> 
> Best -- Eric
> 

Ok that's really perfect!
The only "problem" is that it keeps exporting the code even without
the :exports none, maybe I need some newlines?

**** s2
#+BEGIN_SRC dot :file s2.pdf :cmdline -Tpdf :exports none :results silent
    digraph s1 {
    t1;
    t2;
    }
#+END_SRC

    [[file:s2.pdf]]

  reply	other threads:[~2009-11-10 17:13 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
2009-11-10 15:41         ` Eric Schulte
2009-11-10 17:13           ` andrea Crotti [this message]
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=loom.20091110T180649-44@post.gmane.org \
    --to=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).