From mboxrd@z Thu Jan 1 00:00:00 1970 From: Achim Gratz Subject: Re: [RFC] Org syntax (draft) Date: Sun, 17 Mar 2013 08:18:12 +0100 Message-ID: <87vc8qqytn.fsf@Rainer.invalid> References: <8738w7c5fh.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([208.118.235.92]:51245) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UH7ra-00071c-D5 for emacs-orgmode@gnu.org; Sun, 17 Mar 2013 03:18:39 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UH7rY-00033f-Da for emacs-orgmode@gnu.org; Sun, 17 Mar 2013 03:18:38 -0400 Received: from plane.gmane.org ([80.91.229.3]:59629) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UH7rY-00033b-71 for emacs-orgmode@gnu.org; Sun, 17 Mar 2013 03:18:36 -0400 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1UH7rs-0002Nx-0a for emacs-orgmode@gnu.org; Sun, 17 Mar 2013 08:18:56 +0100 Received: from pd9eb5fdd.dip.t-dialin.net ([217.235.95.221]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 17 Mar 2013 08:18:56 +0100 Received: from Stromeko by pd9eb5fdd.dip.t-dialin.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 17 Mar 2013 08:18:56 +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 Nicolas Goaziou writes: > As discussed a few days ago, here is a document describing the complete > Org syntax as read by the parser. I also added some comments. I am going > to put the Org file on Worg, so anyone can update it and fix mistakes. after some playing with the Org manual in Org that Tom has been working on I am starting to think that there should be a way to define the same macro differently for different export backends. That would be mainly so that you could have a macro expansion use export snippets tailored to that backend where (after stripping the export snippets) the expansion makes little or no sense in other backends. What do you think? Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ DIY Stuff: http://Synth.Stromeko.net/DIY.html