From: Nick Dokos <ndokos@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: cannot export to beamer.
Date: Mon, 17 Dec 2018 09:20:27 -0500 [thread overview]
Message-ID: <87y38ow7ys.fsf@alphaville.usersys.redhat.com> (raw)
In-Reply-To: 8736qy8yl4.fsf@mat.ucm.es
Uwe Brauer <oub@mat.ucm.es> writes:
>>>> "Ken" == Ken Mankoff <mankoff@gmail.com> writes:
>
> > On 2018-12-15 at 09:38 -0800, Uwe Brauer <oub@mat.ucm.es> wrote:
> >> I am very used to the beamer style and it works on my machine quite
> >> well.
>
> > But it doesn't work quiet well according to this email. What
> > changed? Are you on a new machine? Is LaTeX installed?
>
> I don't understand. When I create (using emacs and auctex) a beamer
> document I can compile it without problem.
>
> What does not work is exporting the example org file to a working latex
> (beamer) file.
>
> It seems that I have to set up, manually (sigh!)
>
> Org-latex-classes. That is quite annoying I thought the beamer class
> would be included.
>
I think Ken was pointing out that export to beamer is a different operation
than exporting to latex: you use C-c l l (e.g.) for the latter, but C-c l b
for the former. Maybe that's where you get hung up?
--
Nick
"There are only two hard problems in computer science: cache
invalidation, naming things, and off-by-one errors." -Martin Fowler
next prev parent reply other threads:[~2018-12-17 14:20 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-15 17:38 cannot export to beamer Uwe Brauer
2018-12-15 17:49 ` Ken Mankoff
2018-12-15 17:54 ` Uwe Brauer
2018-12-17 14:20 ` Nick Dokos [this message]
2018-12-15 18:14 ` Josiah Schwab
2018-12-15 18:48 ` Colin Baxter
2018-12-15 19:30 ` Uwe Brauer
2018-12-15 20:43 ` Uwe Brauer
2018-12-16 10:25 ` Eric S Fraga
2018-12-16 18:16 ` Uwe Brauer
2018-12-16 19:21 ` Tim Cross
2018-12-16 21:01 ` Uwe Brauer
2018-12-16 21:36 ` Tim Cross
2018-12-16 19:46 ` Ken Mankoff
2018-12-16 21:11 ` Uwe Brauer
2018-12-16 22:37 ` Eric S Fraga
2018-12-17 8:02 ` Uwe Brauer
2018-12-17 9:53 ` 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=87y38ow7ys.fsf@alphaville.usersys.redhat.com \
--to=ndokos@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).