emacs-orgmode
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [O] [latex] Problems with old exporter (for Beamer) and with new exp


From: Sebastien Vauban
Subject: Re: [O] [latex] Problems with old exporter (for Beamer) and with new exporter
Date: Fri, 15 Jun 2012 11:09:26 +0200
User-agent: Gnus/5.130006 (Ma Gnus v0.6) Emacs/24.1 (windows-nt)

Hello Nicolas,

Nicolas Goaziou wrote:
> "Sebastien Vauban"
> <address@hidden> 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




reply via email to

[Prev in Thread] Current Thread [Next in Thread]