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 18:23:48 +0200 [thread overview]
Message-ID: <17EF489F-9B9B-4510-A7D5-4B23C08E6691@gmail.com> (raw)
In-Reply-To: <87fxg76yln.fsf@gollum.intra.norang.ca>
On Apr 17, 2009, at 6:20 PM, Bernt Hansen wrote:
> Ah okay. I created that block using Eric's block YASnippet and didn't
> even think about the end tag being wrong (since it added that
> automagically for me when I typed in the block stuff...)
>
> I'll fix my snippet.
And I fixed org-exp-blocks to be more forgiving :-)
- Carsten
>
> Thanks!
>
> Bernt
>
>
> Carsten Dominik <carsten.dominik@gmail.com> writes:
>
>> 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
prev parent reply other threads:[~2009-04-17 16:24 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
2009-04-17 16:20 ` Bernt Hansen
2009-04-17 16:23 ` Carsten Dominik [this message]
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=17EF489F-9B9B-4510-A7D5-4B23C08E6691@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).