From: Sebastien Vauban <sva-news-D0wtAvR13HarG/iDocfnWg@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: Embedding diagrams in Org
Date: Thu, 19 Feb 2015 09:49:01 +0100 [thread overview]
Message-ID: <86pp96jngi.fsf@example.com> (raw)
In-Reply-To: olu61azggdn.fsf@med.uni-goettingen.de
Hello Andreas,
Andreas Leha wrote:
> I also use tikz in my org files. I just include a slightly more
> involved version of Eric's example to show some of the beauty of org.
>
> This includes a caption for the diagram, and different output formats
> for different export routes.
>
> #+LATEX_HEADER: \usepackage{tikz}
>
> * tikz example
>
> #+name: tikz_example
> #+header: :packages '(("" "tikz"))
> #+header: :file (by-backend (latex "example_diagram.tikz") (html "example_diagram.svg") (t "example_diagram.png"))
Where is the `by-backend' function defined?
> #+header: :imagemagick yes :iminoptions -density 600 :imoutoptions -geometry 800
> #+header: :results file raw
> #+header: :fit yes
> #+begin_src latex
> \begin{tikzpicture}
> \node[red!50!black] (a) {A};
> \node (b) [right of=a] {B};
> \draw[->] (a) -- (b);
> \end{tikzpicture}
> #+end_src
>
> #+caption: A tikz example diagram with a caption
> #+results: tikz_example
> [[file:example_diagram.png]]
What'd be nice is that you could say (in a *file* property) that the
extension for LaTeX always has to be .tikz, for HTML .svg and .png in
all the other cases.
Then, you could simply give the base name of the figure where
appropriate, in a "DRY" configuration.
Best regards,
Seb
--
Sebastien Vauban
next prev parent reply other threads:[~2015-02-19 8:49 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-18 12:34 Embedding diagrams in Org Marcin Borkowski
2015-02-18 14:19 ` Eric S Fraga
2015-02-18 15:51 ` Eduardo Ochs
2015-02-18 19:01 ` Eric S Fraga
2015-02-19 8:45 ` Sebastien Vauban
2015-02-18 19:37 ` Andreas Leha
2015-02-19 8:49 ` Sebastien Vauban [this message]
2015-02-21 11:06 ` Andreas Leha
2015-02-19 14:10 ` Eric S Fraga
2015-03-21 11:23 ` Marcin Borkowski
2015-03-21 21:41 ` Andreas Leha
2015-02-24 0:01 ` Marcin Borkowski
2015-02-24 8:04 ` Eric S Fraga
2015-02-24 17:00 ` Charles C. Berry
2015-03-05 8:51 ` Sebastien Vauban
2015-03-04 19:19 ` Marcin Borkowski
2015-03-04 19:37 ` Rasmus
2015-03-04 21:22 ` Andreas Leha
2015-03-05 8:12 ` 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=86pp96jngi.fsf@example.com \
--to=sva-news-d0wtavr13harg/idocfnwg@public.gmane.org \
--cc=emacs-orgmode-mXXj517/zsQ@public.gmane.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).