emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Rasmus <rasmus@gmx.us>
Cc: emacs-orgmode@gnu.org
Subject: Re: [bug?][ox-beamer] hyperref crashes when options are specified
Date: Wed, 28 May 2014 17:44:49 +0200	[thread overview]
Message-ID: <87oayhoqku.fsf@gmail.com> (raw)
In-Reply-To: <8738fuov59.fsf@gmx.us> (rasmus@gmx.us's message of "Wed, 28 May 2014 16:06:10 +0200")

Hello,

Rasmus <rasmus@gmx.us> writes:

> If you give hyperref options when exporting to Beamer it will
> typically crash.
>
> I load hyperref as follows to make it compatible with "exotic"
> headlines in XeLaTeX:
>
>   (setq org-latex-default-packages-alist
>         '(("" "iftex" nil)
>           ("" "fixltx2e" nil)
>           ("AUTO" "inputenc" t)
>           ("T1" "fontenc" t)
>           ("AUTO" "babel" nil)
>           ("" "scrpage2" nil)
>           ("" "graphicx" t)
>           ("" "amsmath" t)
>           ("" "amssymb" t)
>           ("" "booktabs" t)
>           ("" "marvosym" t)
>           ("" "microtype" nil)
>           ("" "slantsc" nil)
>           ("unicode, psdextra,hidelinks" "hyperref" nil)))
>
> Because Beamer loads hyperref automatically this will crash.  The
> correct way to load it is through the document class options, e.g.
>
>      \documentclass[hyperref={unicode, psdextra,hidelinks}]{beamer}
>
> Should ox-beamer automatically move the options in this case?

No, it shoudn't. This crash is not really Org's fault.

You could define an appropriate class for `beamer' back-end instead.


Regards,

-- 
Nicolas Goaziou

  reply	other threads:[~2014-05-28 15:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-28 14:06 [bug?][ox-beamer] hyperref crashes when options are specified Rasmus
2014-05-28 15:44 ` Nicolas Goaziou [this message]
2014-05-28 16:47   ` Rasmus
2014-05-28 17:33     ` Nicolas Goaziou

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=87oayhoqku.fsf@gmail.com \
    --to=n.goaziou@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=rasmus@gmx.us \
    /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).