From: "Sebastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: [latex] Problems with old exporter (for Beamer) and with new exporter
Date: Fri, 15 Jun 2012 11:09:26 +0200 [thread overview]
Message-ID: <80haud2b7d.fsf@somewhere.org> (raw)
In-Reply-To: 87vcit93ao.fsf@gmail.com
Hello Nicolas,
Nicolas Goaziou wrote:
> "Sebastien Vauban"
> <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org> 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
next prev parent reply other threads:[~2012-06-15 9:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-07 20:56 [latex] Problems with old exporter (for Beamer) and with new exporter Sebastien Vauban
2012-06-09 20:18 ` Nicolas Goaziou
2012-06-14 13:06 ` Sebastien Vauban
2012-06-14 18:06 ` Nicolas Goaziou
2012-06-15 9:09 ` Sebastien Vauban [this message]
2012-06-18 7:40 ` Eric S Fraga
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=80haud2b7d.fsf@somewhere.org \
--to=wxhgmqzgwmuf-genee64ty+gs+fvcfc7uqw@public.gmane.org \
--cc=emacs-orgmode-mXXj517/zsQ@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).