From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eric Schulte Subject: Re: [ANN] BREAKING CHANGE -- removing #+BABEL file-wide property lines Date: Thu, 20 Oct 2011 14:12:57 -0600 Message-ID: <87fwinifqu.fsf@gmail.com> References: <87pqhrih3s.fsf@gmail.com> <30891.1319141196@alphaville.dokosmarshall.org> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([140.186.70.92]:35789) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RGyzA-00071v-MI for emacs-orgmode@gnu.org; Thu, 20 Oct 2011 16:13:05 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RGyz8-0004dP-If for emacs-orgmode@gnu.org; Thu, 20 Oct 2011 16:13:04 -0400 Received: from mail-pz0-f47.google.com ([209.85.210.47]:48987) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RGyz8-0004d8-Ba for emacs-orgmode@gnu.org; Thu, 20 Oct 2011 16:13:02 -0400 Received: by pzd13 with SMTP id 13so8576150pzd.6 for ; Thu, 20 Oct 2011 13:13:01 -0700 (PDT) In-Reply-To: <30891.1319141196@alphaville.dokosmarshall.org> (Nick Dokos's message of "Thu, 20 Oct 2011 16:06:36 -0400") 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: nicholas.dokos@hp.com Cc: Org Mode Nick Dokos writes: > Eric Schulte wrote: > >> I have just pushed up a change to the Org-mode git repository which >> removes support for #+BABEL lines. Please use the more general >> #+PROPERTIES lines instead. >> > > Coming late to the dance - sorry. I think that's very confusing. > "Property" is an overloaded term in org: we now have the :PROPERTIES: > drawer, the #+PROPERTY line and the #+PROPERTIES line (singular and > plural forms are already pretty bad). Do the #+PROPERTY and #+PROPERTIES lines have different semantics? > Also, there is the general concept of properties (the stuff that the > property API applies to). > > Unless there is an underlying unity of which I'm unaware, I'd strongly > suggest another term - perhaps CODE_BLOCK_HEADER_ARGUMENTS (plus > an easy-template for easy insertion). > Code blocks already piggy-back off of subtree properties pulling their header arguments out of the properties specified on the subtree level. Given that header arguments and properties are already thus interleaved I believe that properties should be used on the file-wide level as well, rather than introducing another synonymous keyword which adds no new functionality. Does that make sense? Best -- Eric -- Eric Schulte http://cs.unm.edu/~eschulte/