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 18:13:58 +0200 [thread overview]
Message-ID: <87ppqh4g55.fsf@syk.fi> (raw)
In-Reply-To: CA+vqiLG8hzFnVij0=dMX5mukA4HHsksKff6qV369mMKQZQMU3Q@mail.gmail.com
> As far as I know this is a beamer design decision. The idea seems to
> be that if your presentation is short enough that the individual frame
> titles would fit in a table of contents then you don't actually need
> one.
Ok, so be it, I can live with that decision.
All the best,
Jarmo
prev parent reply other threads:[~2013-11-03 16:14 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
2013-11-03 14:18 ` Ista Zahn
2013-11-03 16:13 ` Jarmo Hurri [this message]
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=87ppqh4g55.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).