From mboxrd@z Thu Jan 1 00:00:00 1970 From: orgmode@h-rd.org Subject: Re: [RFC] Org syntax (draft) Date: Tue, 12 Mar 2013 11:19:12 +0100 Message-ID: <20130312111912.Horde.8KkkOWEwhY5RPwEgDbzFaPA@webmailnew.dds.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed; DelSp=Yes Return-path: Received: from eggs.gnu.org ([208.118.235.92]:39811) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UFMIl-000563-Q3 for emacs-orgmode@gnu.org; Tue, 12 Mar 2013 06:19:26 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UFMIh-0000PV-4F for emacs-orgmode@gnu.org; Tue, 12 Mar 2013 06:19:23 -0400 Received: from namiki.dds.nl ([85.17.178.139]:48105) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UFMIg-0000Os-Tk for emacs-orgmode@gnu.org; Tue, 12 Mar 2013 06:19:19 -0400 Content-Disposition: inline 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 Hi Nicolas, great work! It's fantastic that orgmode now gets a specification. What may help is to document the syntax machine readable and somewhat more formal. This ensures that there are less differences in interpretation and that the specification can be used to generate an orgmode parser directly. An example could be how the ietf specifies things, have a look at https://en.wikipedia.org/wiki/ABNF or EBNF. It's not much difference from what you have done, but it's more unambigous. Thanks for the great work!