From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Sebastien Vauban" Subject: Re: [RFC] Org syntax (draft) Date: Sun, 17 Mar 2013 10:36:23 +0100 Message-ID: <86hakafjvs.fsf@somewhere.org> References: <8738w7c5fh.fsf@gmail.com> <87vc8qqytn.fsf@Rainer.invalid> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: 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-mXXj517/zsQ@public.gmane.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org-mXXj517/zsQ@public.gmane.org To: emacs-orgmode-mXXj517/zsQ@public.gmane.org Hi Achim, Achim Gratz wrote: > 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? This is already possible, as once explained by Nicolas on this ML: =E2=95=AD=E2=94=80=E2=94=80=E2=94=80=E2=94=80 =E2=94=82 You can also have macros generating raw code geared towards LaT= eX or HTML =E2=94=82 back-ends (through export-snippets). For example: =E2=94=82=20 =E2=94=82 #+MACRO: my-mod @@e-latex:\something{$1}@@@@e-html:
$1
@@ =E2=94=82=20 =E2=94=82 This is an example: {{{my-mod(text)}}}. =E2=95=B0=E2=94=80=E2=94=80=E2=94=80=E2=94=80 Best regards, Seb --=20 Sebastien Vauban