emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Chris Maier <christopher.maier@gmail.com>
To: Eric S Fraga <e.fraga@ucl.ac.uk>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: [BABEL] Editing dot blocks with org-exp-blocks
Date: Wed, 9 Feb 2011 08:31:00 -0500	[thread overview]
Message-ID: <AANLkTinZzEqawEodyorYr4Z3i548MbbO7Vv7oyPbObFq@mail.gmail.com> (raw)
In-Reply-To: <87hbcd1t94.fsf@pinto.chemeng.ucl.ac.uk>

The begin_dot is part of org-exp-blocks, as I understand it, and
appears required to make it evaluate the Dot code, create the image
file, and then incorporate that into the exported document (LaTeX,
HTML, etc.)

Thanks,
Chris

On Wed, Feb 9, 2011 at 3:56 AM, Eric S Fraga <e.fraga@ucl.ac.uk> wrote:
> Chris Maier <christopher.maier@gmail.com> writes:
>
>> In "normal" Org code blocks (e.g. #+begin_src clojure .... #+end_src)
>> it's possible to hit C-c ' and edit the block code in a separate
>> buffer with the appropriate mode.  This doesn't appear to work when
>> using org-exp-blocks to edit a "begin_dot" block.
>>
>> Is there a command to do this?
>
> No idea but what about using #+begin_src dot ... #+end_src?
> --
> : Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.0.50.1
> : using Org-mode version 7.4 (release_7.4.324.gca7a)
>

  reply	other threads:[~2011-02-09 17:09 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-09  3:50 [BABEL] Editing dot blocks with org-exp-blocks Chris Maier
2011-02-09  8:56 ` Eric S Fraga
2011-02-09 13:31   ` Chris Maier [this message]
2011-02-09 14:10     ` Eric S Fraga
2011-02-09 15:14       ` Dan Davison
2011-02-09 15:39         ` Chris Maier
2011-02-09 16:14           ` Dan Davison
2011-02-10  2:05             ` Chris Maier
2011-02-10  1:05         ` Eric Schulte
2011-02-10 10:05           ` Eric S Fraga
2011-02-10 17:02             ` Eric Schulte
2011-02-09  8:58 ` Sébastien Vauban

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=AANLkTinZzEqawEodyorYr4Z3i548MbbO7Vv7oyPbObFq@mail.gmail.com \
    --to=christopher.maier@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).