emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Eric Schulte" <schulte.eric@gmail.com>
To: henry atting <nsmp_02@online.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: help on ditaa
Date: Thu, 25 Feb 2010 13:04:41 -0700	[thread overview]
Message-ID: <87mxyxxesm.fsf@gmail.com> (raw)
In-Reply-To: <87d3ztqfm5.fsf@online.de> (henry atting's message of "Thu, 25 Feb 2010 20:28:50 +0100")

Hi Henry,

Try pressing C-c C-c with the cursor on your ditaa block.  If an image
is generated and a link inserted into the file, but you're still not
getting an image on export then try making the following change (adding
an exports header argument) to your block

#+begin_src ditaa :file image.png :cmdline -r :exports results
+---------+
| cBLU    |
|         |
|    +----+
|    |cPNK|
|    |    |
+----+----+
#+end_src

otherwise you probably don't have org-babel activated in which case
adding

(require 'org-babel-init)

to your .emacs should help.

Best -- Eric

henry atting <nsmp_02@online.de> writes:

> What exactly is the proper way to export code with ditaa? My knowledge
> must be fragmentary for only the code is exported but the conversion to
> images failes.
>
> I did something like this:
>
> Load the appropriate libs, like org-babel, org-babel-tangle, org-ditaa,
> org-exp-blocks, then set the variable `org-ditaa-jar-path' to the ditaa
> jar file.
>
> The according lines in my org file look like this:
>
>
> #+begin_src ditaa :file image.png :cmdline -r
> +---------+
> | cBLU    |
> |         |
> |    +----+
> |    |cPNK|
> |    |    |
> +----+----+
> #+end_src
>
> henry

  reply	other threads:[~2010-02-25 20:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-25 19:28 help on ditaa henry atting
2010-02-25 20:04 ` Eric Schulte [this message]
2010-02-26 11:53   ` Unknown, henry atting
2010-02-26 15:00   ` henry atting

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=87mxyxxesm.fsf@gmail.com \
    --to=schulte.eric@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=nsmp_02@online.de \
    /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).