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: [babel] dot in pdf directly
Date: Mon, 09 Nov 2009 23:24:08 +0100	[thread overview]
Message-ID: <87fx8n72wn.fsf@gmx.de> (raw)
In-Reply-To: <loom.20091109T221323-745@post.gmane.org> (andrea Crotti's message of "Mon, 9 Nov 2009 21:16:58 +0000 (UTC)")

andrea Crotti <andrea.crotti.0@gmail.com> writes:
> Still a couple of questions, I found something here
> in the newsgroup but nothing helped me...
>
> First, how many and where can I find all the possible
>
> #+begin_...?
>
> I mean why is
> #+begin_dot and not
>
> #+begin_src dot?
>
> I would like to insert my dot info and on exporting getting a pdf with
> embedded the generated eps, it would be great!
>
> I don't have very clear the grammar I can use in the #+begin_.. line,
> is there a clear explanation somewhere?


The difference is, 

   #+begin_src mode-name

just tells the exporter that the following block is a `mode-name' block,
where mode-name == the name of the emacs mode you'd use to edit a file
in that language.

This handy if you want to edit the block's contents (C-c '). Eventually,
the source code inside the block will be highlighted on export to
XHTML. The mode is important then, too. Contents of blocks like this are
exported verbatim.




In contrast, blocks like

   #+begin_ditaa

will never export verbatim. Instead, the contents are treated specially
or even send to an external program, that will create an image (e.g. -
in most cases), that will in turn replace the block in the exported
result.


  Sebastian

  reply	other threads:[~2009-11-09 22:24 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 [this message]
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
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=87fx8n72wn.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).