From mboxrd@z Thu Jan 1 00:00:00 1970 From: Florian Beck Subject: Re: Some Experiences with org-babel-load-file Date: Tue, 11 Dec 2012 20:52:39 +0100 Message-ID: <50C78F07.3090509@miszellen.de> References: <50C66343.2010202@miszellen.de> <87ip88mpxa.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from eggs.gnu.org ([208.118.235.92]:45667) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TiVsq-0001nJ-Mf for emacs-orgmode@gnu.org; Tue, 11 Dec 2012 14:53:00 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TiVsl-00059P-P1 for emacs-orgmode@gnu.org; Tue, 11 Dec 2012 14:52:52 -0500 Received: from mo6-p04-ob.rzone.de ([2a01:238:20a:202:5304::1]:46397) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TiVsl-000587-IF for emacs-orgmode@gnu.org; Tue, 11 Dec 2012 14:52:47 -0500 Received: from [10.52.86.239] ([82.113.98.239]) by smtp.strato.de (jorabe mo3) (RZmta 31.8 SBL|AUTH) with ESMTPA id g05608oBBJaYy6 for ; Tue, 11 Dec 2012 20:52:41 +0100 (CET) In-Reply-To: <87ip88mpxa.fsf@gmail.com> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org On 12/11/2012 03:52 PM, Eric Schulte wrote: > Please go ahead and update the information on worg. Note that Emacs24 > users need only do > > (require 'org) > (org-babel-load-file "/path/to/your/org-init-file.org") > > while users of lesser Emacs will have to load a new version of Org-mode > before calling org-babel-load-file. Sorry, I have no idea how to update worg. > compiled and un-compiled code. If this does pose a problem for you, > perhaps an optional extra argument to be added to org-babel-load-file to > enable compilation. Yes, this would do nicely. > The `org-babel-load-file' function calls `org-tangle-file' so they are > definitely working in concert. When a target file is passed to > `org-tangle-file' then that is used as the value of the ":tangle" header > argument, so the default behavior is to tangle. Ok, that makes sense. > Great idea. I don't have time to work on this right now, but it is > definitely on my stack. I suppose this should be the default behavior > for all tangled files (not just those written by org-babel-load-file). Yes. Perhaps also include a comment that the file was tangled from an org-file plus the path to that file.