[Orgmode] Ditaa and babel goofing again?

2010-09-01 Thread John Hendy
Hi, See this post for reference: http://www.mail-archive.com/emacs-orgmode@gnu.org/msg27725.html With that issue, ditaa just wasn't cooperating for some reason. Now everything *appears* to cooperate but I get no output! Completely baffled... Per the mailing list resolution above, I tried the

Re: [Orgmode] Ditaa and babel goofing again?

2010-09-01 Thread Erik Iverson
I see the following in my *Messages* buffer after running. executing Ditaa code block... java -jar /home/fileserv/tacc/eriki/emacs/lisp/org-mode/contrib/scripts/ditaa.jar /tmp/babel-31845pim/ditaa-318455Fo example.png DiTAA version 0.8, Copyright (C) 2004--2009 Efstathios Sideris Running

Re: [Orgmode] Ditaa and babel goofing again?

2010-09-01 Thread John Hendy
Okay, fixed it on a whim but clueless as to why this was the issue: 1) (setq org-ditaa-jar-path ~/.elisp/org.git/contrib/scripts/ditaa.jar) 2) (setq org-ditaa-jar-path /home/jwhendy/.elisp/org.git/contrib/scripts/ditaa.jar) #1 *does not* work; #2 does! Should I have known this would be a

Re: [Orgmode] Ditaa and babel goofing again?

2010-09-01 Thread Juan
Had the same problem somewhere in july. I think it was after the following commit: commit 7d2dc48b2aae27a66cc9813797c14dd457c209f4 Author: Gregory J. Grubbs greg...@dynapse.com Date: Sun Jul 18 09:01:24 2010 + Quote path argument in ob-ditaa * lisp/ob-ditaa.el

Re: [Orgmode] Ditaa and babel goofing again?

2010-09-01 Thread Eric Schulte
I've just pushed up a fix to this issue, both ~'s and spaces should work now. -- Eric Juan pech...@computer.org writes: Had the same problem somewhere in july. I think it was after the following commit: commit 7d2dc48b2aae27a66cc9813797c14dd457c209f4 Author: Gregory J. Grubbs

Re: [Orgmode] Ditaa and babel goofing again?

2010-09-01 Thread John Hendy
Awesome. Thanks! John On Thu, Sep 2, 2010 at 12:09 AM, Eric Schulte schulte.e...@gmail.comwrote: I've just pushed up a fix to this issue, both ~'s and spaces should work now. -- Eric Juan pech...@computer.org writes: Had the same problem somewhere in july. I think it was after the