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, 03 Nov 2011 12:40:19 -0600 Message-ID: <87fwi5gics.fsf@gmail.com> References: <87pqhrih3s.fsf@gmail.com> <87zkgvfhra.fsf@gmail.com> <2127.1319148505@alphaville.dokosmarshall.org> <87vcrjfgt1.fsf@gmail.com> <80sjmmvm60.fsf@somewhere.org> <4EA129DB.4070006@christianmoe.com> <8762ji5jr6.fsf@gmail.com> <4EA1D4F9.5010302@christianmoe.com> <4ea1de9c.67b4ec0a.553d.122a@mx.google.com> <87aa8t10np.fsf@gmail.com> <4ea5a95b.059dec0a.606e.0c92@mx.google.com> <874nypkn6y.fsf@gmail.com> <87obwwkia5.fsf@gmail.com> <87boswk4vj.fsf@gmail.com> <8627.1320157576@alphaville.dokosmarshall.org> <9991.1320159724@alphaville.dokosmarshall.org> <87hb2nj2ic.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([140.186.70.92]:50459) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RM2GL-0000fA-Sz for emacs-orgmode@gnu.org; Thu, 03 Nov 2011 14:43:43 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RM2GK-0004Oa-Lf for emacs-orgmode@gnu.org; Thu, 03 Nov 2011 14:43:41 -0400 Received: from mail-gy0-f169.google.com ([209.85.160.169]:43243) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RM2GK-0004ON-GE for emacs-orgmode@gnu.org; Thu, 03 Nov 2011 14:43:40 -0400 Received: by gyg10 with SMTP id 10so1913169gyg.0 for ; Thu, 03 Nov 2011 11:43:39 -0700 (PDT) In-Reply-To: (Rainer M. Krug's message of "Wed, 2 Nov 2011 12:12:06 +0100") 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: Rainer M Krug Cc: nicholas.dokos@hp.com, emacs-orgmode@gnu.org >> > >> > In order to prevent confusion or needless argument: the path I >> >think we should back off of is the committing of these changes to >> >master - I think the work should be done in a branch and cooked >> >thoroughly before merging it to master. >> > >> > > Partly agree here - I was bitten by the changes, and have suspended work on > one project until this issue stabilizes - I do not want to change my files > after each change. > Hi Rainer, In a previous thread in which you were included I suggested a solution which works now and will continue to work in the future no matter how this issue is resolved. That solution is to use a multi-line file local variable [1] to customize the org-babel-default-header-args variable. I should have made a bigger deal of this solution when I posted it the first time, my apologies. In general I think we do a good job of not breaking functionality without on this master branch, and I think that introducing a multitude of branches would only serve to add confusion, reduce org-wide cooperation, and ultimately only delay rather than somehow remove them. Best -- Eric Footnotes: [1] to see the info page evaluate (info "(elisp)File Local Variables") -- Eric Schulte http://cs.unm.edu/~eschulte/