From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Brand Subject: Re: :session question -- and changes to #+Property: syntax Date: Wed, 19 Jun 2013 12:10:01 +0200 Message-ID: References: <51501AF2.1070405@easy-emacs.de> <8738vjugwd.fsf@gmail.com> <51516699.6090604@gmail.com> <87ip4ezf93.fsf@med.uni-goettingen.de> <87fvzi72ve.fsf@gmail.com> <87ip4e5gai.fsf@gmail.com> <87k3nmd5es.fsf@Rainer.invalid> <87sj264o0f.fsf@gmail.com> <87k3n8gf47.fsf@Rainer.invalid> <878v2l7v7s.fsf@Rainer.invalid> <87txl9u4c4.fsf_-_@gmail.com> <87d2rjcfsv.fsf@Rainer.invalid> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:41835) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UpFL5-0006Xh-Fr for emacs-orgmode@gnu.org; Wed, 19 Jun 2013 06:10:08 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UpFL0-0005xC-Lu for emacs-orgmode@gnu.org; Wed, 19 Jun 2013 06:10:07 -0400 Received: from mail-la0-x234.google.com ([2a00:1450:4010:c03::234]:44194) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UpFL0-0005uI-Cw for emacs-orgmode@gnu.org; Wed, 19 Jun 2013 06:10:02 -0400 Received: by mail-la0-f52.google.com with SMTP id fo12so4366244lab.25 for ; Wed, 19 Jun 2013 03:10:01 -0700 (PDT) In-Reply-To: <87d2rjcfsv.fsf@Rainer.invalid> 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: Achim Gratz Cc: Org Mode Hi Achim On Tue, Jun 18, 2013 at 10:41 PM, Achim Gratz wrote: > Hi Eric, > > while starting to write up a test document I've found some behaviour > when executing LOB calls that warrant discussion, I think: > > 1. The properties are evaluated at the site of the definition rather > than the site of the call. This is simply how org-babel-process-params > works, it jumps to the definition and then executes the source block > there (this may be in another file even). > > 2. The evaluation of header arguments assumes emacs-lisp as a language. I guess you do not mean the language of the source block, else see below for an example with shell. > > > These two combined make it somewhat difficult to use properties to > control the behaviour of LOB calls and understand what is happening and > why. A workaround is to beam the source to the place of call via noweb > syntax. The first point could perhaps be addressed in a cleaner way by > using org-babel-current-src-block-location when calling org-entry-get, > but I'm not sure yet if it is always correctly set. My intention is to ensure this with an ERT, see my patch here: http://lists.gnu.org/archive/html/emacs-orgmode/2013-06/msg00738.html > [...] Michael