From: Jarmo Hurri <jarmo.hurri@syk.fi>
To: emacs-orgmode@gnu.org
Subject: Re: Beamer export: one question and one bug
Date: Sun, 03 Nov 2013 12:06:28 +0200 [thread overview]
Message-ID: <8761s9ztnf.fsf@syk.fi> (raw)
In-Reply-To: CA+vqiLH7b1_5S_sFMWKKikcw84VDMLabS+=Xdsd7X5g_gYe-vg@mail.gmail.com
Greetings.
> Set '#OPTIONS: H:2', then top level headlines become sections (and are
> listed in the table of contents) and second-level headlines become the
> frames.
Yep, that will happen. However, the original idea was to get frame
headlines into the table of contents. In order to achieve this I would
have to have H:2 and repeat the frame title as follows:
# --------------------------------------------------------------------
#+TITLE: Beamer test
#+OPTIONS: ':nil *:t -:t ::t <:t H:2 \n:nil ^:t arch:headline
#+OPTIONS: author:t c:nil creator:comment d:(not LOGBOOK) date:t e:t
#+OPTIONS: email:nil f:t inline:t num:t p:nil pri:nil prop:nil stat:t
#+OPTIONS: tags:t tasks:t tex:t timestamp:t toc:t todo:t |:t
#+CREATOR: Emacs 24.2.1 (Org mode 8.2.1)
#+DESCRIPTION:
#+EXCLUDE_TAGS: noexport
#+KEYWORDS:
#+LANGUAGE: en
#+SELECT_TAGS: export
* This is the first slide
** This is the first slide
- with some fancy text
* And this is the second slide
** And this is the second slide
- with one commented item...
# --------------------------------------------------------------------
The output is correct, but requires duplication of information, which is
practically always a bad idea.
Jarmo
next prev parent reply other threads:[~2013-11-03 10:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-25 11:58 Beamer export: one question and one bug Jarmo Hurri
2013-10-25 18:56 ` Nicolas Goaziou
2013-10-26 7:20 ` Jarmo Hurri
2013-10-27 1:31 ` Nick Dokos
2013-10-27 9:10 ` Jarmo Hurri
2013-10-28 14:13 ` Nick Dokos
2013-11-02 14:10 ` Ista Zahn
2013-11-03 10:06 ` Jarmo Hurri [this message]
2013-11-03 14:18 ` Ista Zahn
2013-11-03 16:13 ` Jarmo Hurri
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=8761s9ztnf.fsf@syk.fi \
--to=jarmo.hurri@syk.fi \
--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).