From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Eric Schulte" Subject: Re: [BABEL] "unset" :var definitions for subtree Date: Sat, 12 Feb 2011 16:13:11 -0700 Message-ID: <87zkq03ky3.fsf@gmail.com> References: <4D500BEC.1080300@gmail.com> <87bp2koeir.fsf@gmail.com> <4D53A2D2.2080300@gmail.com> <87r5bfn8dg.fsf@gmail.com> <87bp2imzb7.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from [140.186.70.92] (port=56954 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PoOfD-0001vN-2P for emacs-orgmode@gnu.org; Sat, 12 Feb 2011 18:14:04 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1PoOfC-0005ih-07 for emacs-orgmode@gnu.org; Sat, 12 Feb 2011 18:14:03 -0500 Received: from mail-pz0-f41.google.com ([209.85.210.41]:33395) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1PoOfB-0005gZ-Pc for emacs-orgmode@gnu.org; Sat, 12 Feb 2011 18:14:01 -0500 Received: by mail-pz0-f41.google.com with SMTP id 27so806327pzk.0 for ; Sat, 12 Feb 2011 15:14:01 -0800 (PST) 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: Dan Davison Cc: emacs-orgmode , Rainer M Krug [...] > > I agree, the things I was talking about don't end up being simpler in > terms of usage for this case. My thinking was that variable unsetting > might be something that would be required fairly rarely, and so it might > be worth appropriate to support it as part of a more general/powerful > mechanism tied into Org properties, or even that hook. > It does sound like if there were a way to disable inheritance for certain properties for certain sub-trees of a document, then that would be ideal -- although I can't imagine how such functionality would be implemented. Can we think of an Org-wide syntax for disinheriting specific properties? > > Before we proceed with the variable unsetting, could someone provide a > motivating example, just to convince ourselves that the extra features > are justified? (The conclusion of another message was that the torque > script example was more a motivating example for shebang/preamble > processing than for variable unsetting.) > Certainly. 1. taking Rainer's first example, lets say that you want a variable specified for all but one code block in a file (maybe that one code block is the source of the value of the variable). In this case it would be much simpler to specify the variable file-wide, and then unset the variable for that one code block. 2. say you want the same session for /nearly/ every code block in a file. 3. same for :dir, :file, or :shebang... So, in summary, I am all for a general org-mode wide solution for disinheriting specific properties, however, if we are unable to find such a solution then I would lean towards implementing this for Babel specifically. Best -- Eric