From: Michal Sojka <sojka@os.inf.tu-dresden.de>
To: emacs-orgmode@gnu.org
Subject: Mediawiki export bugs and export to Doxygen
Date: Wed, 24 Aug 2011 11:55:33 +0200 [thread overview]
Message-ID: <87hb5716cq.fsf@steelpick.2x.cz> (raw)
Hi all,
I wanted to try the experimental Mediawiki exporter and it fails to
export documents with dot code blocks (as the one provided below). I
tried to fix that myself but my elisp and org-babel knowledge is not
sufficient for that. I used org-mode 7.7.
The error was: "file-name-extension: Wrong type argument: stringp, nil".
I tracked it down and it seems that it is caused by (nth 2 info) being
nil in org-babel-exp-do-export, whereas in org-babel-exp-src-block,
which calls org-babel-exp-do-export, the information about :file and
:cmdline is still present.
Another problem is that the Mediawiki export doesn't obey the
org-confirm-babel-evaluate variable - it always wants to confirm the
evaluation of code block.
I have also seen
http://thread.gmane.org/gmane.emacs.orgmode/40746/focus=40749 but this
seems to solve different thing. Does anybody have a suggestion how to
solve this.
Additionally, I'm thinking about writing org exporter to Doxygen syntax.
I wanted to based it on Mediawiki exporter but I'm not sure whether it
is a good idea since the Mediawiki exporter doesn't seem to be
maintained. Again, any suggestions are welcomed.
And finally, the example that fails to export to mediawiki:
--8<---------------cut here---------------start------------->8---
#+TITLE: Test
#+begin_src dot :file generic_proto.png :cmdline -Tpng
digraph com {
in -> out;
in -> call
}
#+end_src
# Local Variables:
# org-confirm-babel-evaluate: nil
# End:
--8<---------------cut here---------------end--------------->8---
Thanks,
-Michal
reply other threads:[~2011-08-24 9:55 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=87hb5716cq.fsf@steelpick.2x.cz \
--to=sojka@os.inf.tu-dresden.de \
--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).