From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Sebastien Vauban" Subject: Re: [latex] Problems with old exporter (for Beamer) and with new exporter Date: Fri, 15 Jun 2012 11:09:26 +0200 Message-ID: <80haud2b7d.fsf@somewhere.org> References: <80ipf2hmdy.fsf@somewhere.org> <87lijwdyte.fsf@gmail.com> <80aa062gbs.fsf@somewhere.org> <87vcit93ao.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain 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 Hello Nicolas, Nicolas Goaziou wrote: > "Sebastien Vauban" > writes: > >>>> With the new exporter, most things work. What does not work: >>>> - macro does not get executed (no string in orange color), >>> >>> Macro are meant to produce contents, not to talk to back-ends. Every text >>> they produce will be protected. >> >> Do you mean the template must be pure text? > > Yes. Pure text or another macro. > >> Do you mean that a thing such as >> http://frozenlock.org/2011/11/05/on-the-fly-key-sequence-insertion/ won't work >> anymore? > > Not at the moment, but macros may change in the future. I'm unsure about > the best level to handle them, but it's probably too high at the moment. > > On the other hand, I would like to avoid too much intersection with > inline Babel calls or src blocks. For example, expansion could happen > before buffer is parsed, like in old exporter. But at the same time, > inline src blocks are executed, so I'm sure the macro could be replaced > with such a block. > > I'm open to discussion about this. I think it makes a lot of sense to consider that macros can't be used in a back-end specific way -- the first reason being that you have no way to tell for which back-end they are written (unlike what we can do with `org-add-link-type' where we can specify different back-end translations). >> Though, now, when trying to export to LaTeX (with the new exporter and >> up-to-date Org[1]), I get an error: > > This is because you're using "beamer" as your LaTeX class, which > probably doesn't have any association in `org-e-latex-classes'. OK. I thought I was working on a pure document. Sorry for the noise. > Note that even if it had one, it wouldn't work as expected since Beamer > is not supported yet (but I'll probably implement a first draft for this > back-end soon). I'll be glad to be your first Beamer tester -- as this is something I use a lot, even if I do use it in its simple form (no multicolumn parameters, and the like). Best regards, Seb -- Sebastien Vauban