emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Andreas Hirczy <ahi@itp.tugraz.at>
To: emacs-orgmode@gnu.org
Subject: ditaa and plantuml exports source code?
Date: Tue, 31 Jan 2017 11:56:16 +0100	[thread overview]
Message-ID: <8ad1f3h50v.fsf@faepop69.tu-graz.ac.at> (raw)

Hi!

Exports from my org files show unwanted source blocks from ditaa in
export. I created a simple example:

###########################################################
#+NAME: TEST
#+BEGIN_SRC ditaa :file pics/test.png :exports results
+---------+
| cBLU    |
|         |
|    +----+
|    |cPNK|
|    |    |
+----+----+
#+END_SRC
###########################################################

which translates to <https://itp.tugraz.at/~ahi/Leben/test.html>,
including both source and result. The documentation at
<http://orgmode.org/manual/Exporting-code-blocks.html> states that
":exports results" is the default for ditaa anyway.

I am rather secure, this worked as intended some time ago; but I get
this behaviour now with at least the following exporters:

 - html
 - latex
 - ODT

I found the same problem with plantuml - see
<https://itp.tugraz.at/~ahi/Leben/WarmwasserHeizung.html#org8b51eec> for
an example.

Is there anybody who experiences the same behaviuor?

My version of org is
Org mode version 9.0.4 (release_9.0.2-129-g2ac798.dirty @ /afs/itp.tugraz.at/user/ahi/.emacs.d/org-mode/lisp/)

Best regards
Andreas
-- 
Andreas Hirczy <ahi@itp.tugraz.at>                  https://itp.tugraz.at/~ahi/
Graz University of Technology                       phone: +43/316/873-   8190
Institute of Theoretical and Computational Physics    fax: +43/316/873-10 8190
Petersgasse 16, A-8010 Graz                        mobile: +43/664/859 23 57

                 reply	other threads:[~2017-01-31 10:56 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=8ad1f3h50v.fsf@faepop69.tu-graz.ac.at \
    --to=ahi@itp.tugraz.at \
    --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).