From mboxrd@z Thu Jan 1 00:00:00 1970 From: John Wiegley Subject: Re: Allowing loose ordering in Org files Date: Mon, 09 Nov 2015 11:24:41 -0800 Message-ID: References: <871tc83p01.fsf@flynn.nichework.com> <84io5j1k5h.fsf@gmail.com> <84611j19hk.fsf@gmail.com> <5638C2A1.2090801@iancu.ch> <87h9l32gfc.fsf@nicolasgoaziou.fr> <87d1vq3mh4.fsf@nicolasgoaziou.fr> <874mh23iw0.fsf@nicolasgoaziou.fr> <878u6eu5wg.fsf@Rainer.invalid> <315DDEDC-1BD9-4680-A8C8-B36821EB931C@gmail.com> <874mh2u2w0.fsf@Rainer.invalid> <87ziytyl3z.fsf@free.fr> <87d1vjyojv.fsf@Rainer.invalid> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:43299) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Zvs3e-0000bT-5w for emacs-orgmode@gnu.org; Mon, 09 Nov 2015 14:24:51 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Zvs3Z-0000lS-9V for emacs-orgmode@gnu.org; Mon, 09 Nov 2015 14:24:50 -0500 Received: from mail-pa0-x22e.google.com ([2607:f8b0:400e:c03::22e]:33417) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Zvs3Z-0000lL-3k for emacs-orgmode@gnu.org; Mon, 09 Nov 2015 14:24:45 -0500 Received: by pabfh17 with SMTP id fh17so208147318pab.0 for ; Mon, 09 Nov 2015 11:24:44 -0800 (PST) Received: from Vulcan.attlocal.net (76-234-68-79.lightspeed.frokca.sbcglobal.net. [76.234.68.79]) by smtp.gmail.com with ESMTPSA id ce3sm17853093pbb.35.2015.11.09.11.24.43 for (version=TLS1 cipher=AES128-SHA bits=128/128); Mon, 09 Nov 2015 11:24:43 -0800 (PST) In-Reply-To: <87d1vjyojv.fsf@Rainer.invalid> (Achim Gratz's message of "Mon, 09 Nov 2015 20:12:52 +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: emacs-orgmode@gnu.org >>>>> Achim Gratz writes: > The whole point of defining a formal syntax for Org is that it becomes > possible to parse Org documents with something other than Emacs and still > make sense of them. To reap that benefit, you need to drop some of the > ad-hoc parsing that Org did in the past. Yes, I know this. The benefits of regular structure are unrelated to my request for freedom from the constraints of such regularity. > You will find that the argument really wasn't about performance, but > complexity. I can accept a complexity argument, if my request were really "a separate code-path". I'm not sure it is. For example, my needs could be satisfied by something as simple as: (defun parse-org-entry (...) (let ((props (funcall 'parse-org-properties-function ...))) ...)) `parse-org-properties-function' would point to a function that does what Org 8.3 does now. This gives me the option of porting over the 8.2 version and keeping the old behavior. All that needs to be done is to allow this hook, no? John