From: Carsten Dominik <carsten.dominik@gmail.com>
To: Marvin Doyley <doyley@ece.rochester.edu>
Cc: emacs-orgmode@gnu.org
Subject: Re: Problem org-beamer export
Date: Fri, 14 May 2010 14:08:42 +0200 [thread overview]
Message-ID: <07698044-5B4A-4310-8104-0D1F601D027F@gmail.com> (raw)
In-Reply-To: <1D4E2F50-1859-435B-AE42-C3B36EA0C37D@ece.rochester.edu>
On May 13, 2010, at 5:16 PM, Marvin Doyley wrote:
> Hi there,
>
> Org beamer has proven to be an invaluable tool, I use it not only
> for preparing lecture notes but also for all my presentation -
> farewell powerpoint :) However, I recently upgraded my current
> version of org to 6.36. I love the new inline image, but their seem
> to be a bug in the latex export. It would appear that org-export-
> latex still does a good job in translating org files to latex, but
> for some reason I get an error when issue C-C C-e C-p . More
> specifically, pdftex.def Error: Option 'pdftex' requires pdfTex.
> What is interesting is 1) if I compile the resulting latex file from
> the command line everything works fine, 2) I don't get an error
> when there is an existing pdf file when I issue C-C C-e C-p, but
> the pdf doesn't get updated - it seems to skip the compiling stage
> if the pdf file is there.
Hi,
I have no problems compiling to PDF. Anyone else?
The error message sounds to me that somehow Emacs cannot find the you
TEX installation. Maybe there is something wrong with the paths. If
it works from the command line, try starting Emacs from the command
line - this will make the command line environment visible to Emacs.
If you start Carbon Emacs normally, then stuff in you shell setup is
not read any you may end up with a different set of environment
settings.
- Carsten
next prev parent reply other threads:[~2010-05-14 12:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-13 15:16 Problem org-beamer export Marvin Doyley
2010-05-14 12:08 ` Carsten Dominik [this message]
2010-05-14 13:11 ` Marvin Doyley
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=07698044-5B4A-4310-8104-0D1F601D027F@gmail.com \
--to=carsten.dominik@gmail.com \
--cc=doyley@ece.rochester.edu \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.