From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Eric Schulte" Subject: Re: Re: bug: babel-* dirs Date: Fri, 01 Oct 2010 14:09:57 -0600 Message-ID: <87zkuxk739.fsf@gmail.com> References: <87occ4qf5e.fsf@Rainer.invalid> <87iq29eitg.fsf@gmail.com> <87hbh7i767.fsf@gmail.com> <87lj6hhezw.fsf@Rainer.invalid> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from [140.186.70.92] (port=55285 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1P1lvk-0001x8-Va for emacs-orgmode@gnu.org; Fri, 01 Oct 2010 16:10:10 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1P1lvj-00066c-PT for emacs-orgmode@gnu.org; Fri, 01 Oct 2010 16:10:08 -0400 Received: from mail-pw0-f41.google.com ([209.85.160.41]:52745) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1P1lvj-00066U-J0 for emacs-orgmode@gnu.org; Fri, 01 Oct 2010 16:10:07 -0400 Received: by pwj6 with SMTP id 6so2010343pwj.0 for ; Fri, 01 Oct 2010 13:10:06 -0700 (PDT) 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: Achim Gratz Cc: emacs-orgmode@gnu.org Achim Gratz writes: > "Eric Schulte" writes: >> I've re-enabled this functionality, I believe the problems should be >> fixed, from the commit message... > > Byte compile warns: > > In org-babel-temp-file: > ob.el:1792:36:Warning: reference to free variable > `org-babel-temporary-directory' > Fixed the byte-compilation warning, thanks for the catch. > > In addition, byte-compiling produces 173 empty /tmp/babel-* > directories. > > The newly installed version does not produce a temporary directory (I'm > not using babel yet), but calling up emacs like make does (extending the > load-path and not sourcing the site-file) will produce one that does not > go away after Emacs is closed on each start of emacs (which explains the > result of byte-compiling). > Thanks for the debugging information, it's great to finally have enough context to address this issue. I've just pushed up what I hope is a fix for this. Thanks -- Eric > > > Achim.