Re: Problem with ditaa when doing export from command line

[Herbert Sitz <hsitz@nwlink.com>]

Nick Dokos <nicholas.dokos <at> hp.com> writes:
>That's a quoting problem (you are on Windoze, right?) The command line
>on Windoze sucks raw eggs (well, not just the command line, but I'm biased .

You are correct, sir!  Thanks, it is indeed a quoting problem.

> 
> On Linux, I used two kinds of quotes in order to protect the 
> vulnerable characters
> inside each lisp sexp (you could also use backslashes strategically):
> 
>    emacs -batch --visit foo.org --eval '(setq org-confirm-babel-evaluate nil)'\
>                                 --eval "(require 'ob-ditaa)"\
>                                 --eval '(setq org-babel-temporary-directory
"tmp")'\
>                                 --eval '(setq org-ditaa-jar-path
"/home/nick/elisp/org-mode/contrib/scripts/ditaa.jar")'\
>                                 --funcall org-export-as-html
> 
> Inconvenient, but it works.

Okay, here's what seems to work on Windoze.  Don't laugh:

emacs -batch --visit foo.org ^
           --eval ^"(setq org-confirm-babel-evaluate nil)^" ^
           --eval ^"(require 'ob-ditaa)^" ^
           --eval ^"(setq org-babel-temporary-directory \^"tmp\^")^" ^
           --eval ^"(setq org-ditaa-jar-path \^"/home/nick/elisp/org-mode
/contrib/scripts/ditaa.jar\^")^" ^
           --funcall org-export-as-html

There is actually some reason to the rhyme, which is explained here:
http://blogs.msdn.com/b/twistylittlepassagesallalike/archive/2011/04/23/everyone-quotes-arguments-the-wrong-way.aspx

Thanks again.

-- Herb