From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nick Dokos Subject: Re: [ANN] BREAKING CHANGE -- removing #+BABEL file-wide property lines Date: Thu, 20 Oct 2011 18:08:25 -0400 Message-ID: <2127.1319148505@alphaville.dokosmarshall.org> References: <87pqhrih3s.fsf@gmail.com> <30891.1319141196@alphaville.dokosmarshall.org> <87fwinifqu.fsf@gmail.com> <32184.1319143892@alphaville.dokosmarshall.org> <87zkgvgxe7.fsf@gmail.com> <1405.1319147324@alphaville.dokosmarshall.org> <87zkgvfhra.fsf@gmail.com> Reply-To: nicholas.dokos@hp.com Return-path: Received: from eggs.gnu.org ([140.186.70.92]:60798) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RH0ms-0003Zs-3g for emacs-orgmode@gnu.org; Thu, 20 Oct 2011 18:08:30 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RH0mr-0006TE-00 for emacs-orgmode@gnu.org; Thu, 20 Oct 2011 18:08:30 -0400 Received: from g1t0026.austin.hp.com ([15.216.28.33]:30306) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RH0mq-0006T8-Qr for emacs-orgmode@gnu.org; Thu, 20 Oct 2011 18:08:28 -0400 In-Reply-To: Message from Eric Schulte of "Thu, 20 Oct 2011 15:57:26 MDT." <87zkgvfhra.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: Eric Schulte Cc: nicholas.dokos@hp.com, Org Mode Eric Schulte wrote: > > Other than "colon confusion" (having to specify ``:results silent'' on > > the src block header line and ``results silent'' in the #+PROPERTY line > > to get the same behavior), this looks better. Not sure what (if > > anything) can or should be done about the colons. > > > > I don't know of a good solution for colons. If we decided to add colons > then the subtree property blocks would become akward, with entries like > > ** foo > :PROPERTIES: > ::results: silent > :END: > > I would say we could look for each value both with and without colons, > but property searches of this nature are slow and doubling the speed > impact simply for allow colon flexibility doesn't seem to be a good > tradeoff. I think this will just have to be something that users will > need to learn. > I agree[fn:1]: the point is to simplify the code, not complicate it *and* slow down everything at the same time. Maybe the header args section of the manual can use the "colon as delimiter" method to explain the equivalent forms and that will suffice. Nick Footnotes: [fn:1] ...but I take some perverse pleasure from the fact that both Suvayu and Seb asked the question :-)