From: Suvayu Ali <fatkasuvayu+linux@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: org-e-beamer missing from org-export-dispatch ui
Date: Wed, 10 Oct 2012 12:22:23 +0200 [thread overview]
Message-ID: <20121010102223.GD6474@kuru.dyndns-at-home.com> (raw)
In-Reply-To: <loom.20121009T222018-324@post.gmane.org>
On Tue, Oct 09, 2012 at 08:24:31PM +0000, bernard wrote:
> Suvayu Ali <fatkasuvayu+linux <at> gmail.com> writes:
>
> >
> > Hi Nicolas and others,
> >
> > The option for beamer export seems to have gone missing from the
> > org-export-dispatch ui. This is how I setup org-e-beamer export in a
> > minimal emacs instance.
> >
> > (setq org-e-latex-pdf-process ; for experimental org-export
> > '("xelatex -interaction nonstopmode -output-directory %o %f"
> > "xelatex -interaction nonstopmode -output-directory %o %f"
> > "xelatex -interaction nonstopmode -output-directory %o %f"))
> >
>
> Thx for sharing.
>
> I have
> (setq org-e-latex-pdf-process
> '("texi2dvi --pdf --clean --verbose --batch %f"))
> grabbed from
> https://lists.gnu.org/archive/html/emacs-orgmode/2012-09/msg01005.html
>
> Could you (or someone else) explain the differences and tradeoffs involved
> between both setups ?
>
Well texi2dvi is very clever and run makeindex or bibtex as needed and
does that quite well until you encounter some of the bugs. In my case I
encountered the infamous regex range in non-standard locales bug.
In conclusion, if texi2dvi works for you, using it is a good option.
HTH
--
Suvayu
Open source is the future. It sets us free.
next prev parent reply other threads:[~2012-10-10 10:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-09 12:39 org-e-beamer missing from org-export-dispatch ui Suvayu Ali
2012-10-09 20:24 ` bernard
2012-10-10 10:22 ` Suvayu Ali [this message]
2012-10-09 20:24 ` Nicolas Goaziou
2012-10-10 10:32 ` 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=20121010102223.GD6474@kuru.dyndns-at-home.com \
--to=fatkasuvayu+linux@gmail.com \
--cc=emacs-orgmode@gnu.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).