Awesome. Thanks!
I've just pushed up a fix to this issue, both ~'s and spaces should work
now. -- Eric
Juan <Pechiar@computer.org> writes:
> Had the same problem somewhere in july. I think it was after the
> following commit:
>
>> commit 7d2dc48b2aae27a66cc9813797c14dd457c209f4
>> Author: Gregory J. Grubbs <gregory@dynapse.com>
>> Date: Sun Jul 18 09:01:24 2010 +0000
>> Quote path argument in ob-ditaa
>> * lisp/ob-ditaa.el (org-babel-execute:ditaa): Quote path to ditaa
>> executable.
>
> that allows spaces in ditaa jar path. Patch was announced to list on
> Sat, 17 Jul 2010 22:01:24 -0600.
>
> The user of (shell-quote-argument org-ditaa-jar-path) seems to disable
> '~' interpretation.
>
> Regards,
> .j.
>
> On Wed, Sep 01, 2010 at 05:17:27PM -0500, John Hendy wrote:
>> 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 problem or is there something else
>> in .emacs that would cause this to require an explicit path vs. the
>> abbreviation of ~ for /home/username?
>
> _______________________________________________
> Emacs-orgmode mailing list
> Please use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org