emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Carsten Dominik <carsten.dominik@gmail.com>
To: Bernt Hansen <bernt@norang.ca>
Cc: emacs-orgmode@gnu.org
Subject: Re: BUG-ditaa export skips drawings
Date: Fri, 17 Apr 2009 17:27:48 +0200	[thread overview]
Message-ID: <FA815187-D84D-4B8C-81E9-5F1125737FB6@gmail.com> (raw)
In-Reply-To: <87vdp4vy1b.fsf@gollum.intra.norang.ca>

Hi Bernt,

org-exp-blocks is confused by the "lisp" in the "#+end_src lisp"
line.

- Carsten

On Apr 17, 2009, at 4:01 AM, Bernt Hansen wrote:

> Hi,
>
> I've run into what I think is a ditaa export bug.  The following file
> doesn't export the first ditaa figure, only the last.
>
> Here's my test file: x.org
> --8<---------------cut here---------------start------------->8---
> #+STARTUP:
> * One
> Here we go!
>
> #+begin_src lisp
> (foo)
> #+end_src lisp
>
> #+begin_ditaa task_states1.png -r -S
> :       +--------+       +---------+       +--------+
> :       |        |       |         |       |        |
> :       |  AAAA  +------>+ STARTED +------>+  DONE  |
> :       | cRED   |       |  cBLU   |       | cGRE   |
> :       +--------+       +---------+       +--------+
> #+end_ditaa
>
> #+begin_ditaa task_states2.png -r -S
> :       +--------+       +---------+       +--------+
> :       |        |       |         |       |        |
> :       |  BBBB  +------>+ STARTED +------>+  DONE  |
> :       | cRED   |       |  cBLU   |       | cGRE   |
> :       +--------+       +---------+       +--------+
> #+end_ditaa
> --8<---------------cut here---------------end--------------->8---
>
> I get the following partial HTML output (I've removed the  
> uninteresting
> parts
>
> x.html:
> --8<---------------cut here---------------start------------->8---
> <p>Here we go!
> </p>
>
>
>
> <pre class="src src-lisp">
> (foo)
> </pre>
>
>
>
>
> :       +--------+       +---------+       +--------+
> :       |        |       |         |       |        |
> :       |  AAAA  +------>+ STARTED +------>+  DONE  |
> :       | cRED   |       |  cBLU   |       | cGRE   |
> :       +--------+       +---------+       +--------+
>
>
>
> <div class="figure">
> <p><img src="task_states2.png"  alt="task_states2.png" /></p>
> </div>
> </div>
> </div>
> --8<---------------cut here---------------end--------------->8---
>
> -Bernt
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Remember: use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode

  reply	other threads:[~2009-04-17 16:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-17  2:01 BUG-ditaa export skips drawings Bernt Hansen
2009-04-17 15:27 ` Carsten Dominik [this message]
2009-04-17 16:20   ` Bernt Hansen
2009-04-17 16:23     ` Carsten Dominik

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=FA815187-D84D-4B8C-81E9-5F1125737FB6@gmail.com \
    --to=carsten.dominik@gmail.com \
    --cc=bernt@norang.ca \
    --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).