From: Suvayu Ali <fatkasuvayu+linux@gmail.com>
To: Nicolas Goaziou <n.goaziou@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [New exporter] Wrong export to LaTeX
Date: Fri, 12 Oct 2012 12:24:34 +0200 [thread overview]
Message-ID: <20121012102434.GA24769@kuru.dyndns-at-home.com> (raw)
In-Reply-To: <877gqw51z9.fsf@gmail.com>
Hi Nicolas,
Let me clarify to see if I understood things correctly.
On Thu, Oct 11, 2012 at 07:54:02PM +0200, Nicolas Goaziou wrote:
>
> > However when I try to export to beamer (Seb's ECM) without the
> >
> > (add-to-list 'org-e-latex-classes '("beamer" ...))
>
> With a minimal setup, the ECM won't export because the file explicitly
> asks for a "beamer" class, which isn't defined.
>
> In other words, you can use Beamer back-end on any class, as long as
> this class is defined in `org-e-latex-classes'. It doesn't have to be
> named "beamer".
>
Okay, I do follow this. However, doesn't LaTeX_CLASS determine what
goes into the \documentclass{class name} directive? If so, does having
\begin{frames}..\end{frames} in the exported tex make sense if the
documentclass directive says, for example, article?
What I'm getting at is, without the LaTeX_CLASS set to beamer, the
crucial \documentclass{beamer} directive is missing and the exported
LaTeX document won't be compilable[1]. Given the preceding comments are
correct, I would then say having a "beamer" class already defined in
org-e-beamer will save new users some trouble. Is my analysis valid, or
am I grossly wrong?
> > bit, I get a backtrace (attached). Is that a bug?
>
> This is strange. The error comes from a void function, although it is
> defined in org.el. I suppose you get the error because you use
> `load-library' instead of `require'. You may want to (load-library
> "org") to fix it.
>
I think I know what went wrong; I had misunderstood your comment
earlier and had exported with the beamer backend Seb's original ECM. Of
course it fails because it explicitly asks for the "beamer" class when
that was not defined.
Cheers,
Footnotes:
[1] I tried this with the LaTeX_CLASS set to article, and there were
errors in the exported pdf.
--
Suvayu
Open source is the future. It sets us free.
next prev parent reply other threads:[~2012-10-12 10:25 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-11 13:04 [New exporter] Wrong export to LaTeX Sebastien Vauban
2012-10-11 13:21 ` Nicolas Goaziou
2012-10-11 16:52 ` Suvayu Ali
2012-10-11 17:54 ` Nicolas Goaziou
2012-10-12 10:24 ` Suvayu Ali [this message]
2012-10-12 11:06 ` Sebastien Vauban
2012-10-12 11:32 ` Sebastien Vauban
2012-10-12 11:51 ` Nicolas Goaziou
2012-10-12 12:15 ` Suvayu Ali
2012-10-12 12:05 ` Suvayu Ali
2012-10-15 20:23 ` Sebastien Vauban
2012-10-15 20:42 ` Nicolas Goaziou
2012-10-16 7:49 ` Sebastien Vauban
2012-10-12 12:09 ` Nicolas Goaziou
2012-10-12 12:19 ` Suvayu Ali
2012-10-11 13:45 ` Suvayu Ali
2012-10-11 14:41 ` Sebastien Vauban
2012-10-11 15:35 ` Suvayu Ali
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=20121012102434.GA24769@kuru.dyndns-at-home.com \
--to=fatkasuvayu+linux@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=n.goaziou@gmail.com \
/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).