From mboxrd@z Thu Jan 1 00:00:00 1970 From: Juan Subject: Re: Ditaa and babel goofing again? Date: Wed, 1 Sep 2010 20:30:40 -0300 Message-ID: <20100901233040.GD2414@soloJazz.com> References: <4C7EC572.3010100@ccbr.umn.edu> <4C7ECE0A.1030000@ccbr.umn.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from [140.186.70.92] (port=49208 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OqwlY-0007UM-Ae for emacs-orgmode@gnu.org; Wed, 01 Sep 2010 19:30:53 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OqwlW-0000aH-O9 for emacs-orgmode@gnu.org; Wed, 01 Sep 2010 19:30:51 -0400 Received: from cpoproxy1-pub.bluehost.com ([69.89.21.11]:34551) by eggs.gnu.org with smtp (Exim 4.69) (envelope-from ) id 1OqwlW-0000Zt-Go for emacs-orgmode@gnu.org; Wed, 01 Sep 2010 19:30:50 -0400 Content-Disposition: inline In-Reply-To: List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: John Hendy Cc: emacs-orgmode Had the same problem somewhere in july. I think it was after the following commit: > commit 7d2dc48b2aae27a66cc9813797c14dd457c209f4 > Author: Gregory J. Grubbs > 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?