From: Suvayu Ali <fatkasuvayu+linux@gmail.com>
To: Nicolas Goaziou <n.goaziou@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [new exporter] #+TOC in beamer export
Date: Wed, 6 Mar 2013 13:09:09 +0100 [thread overview]
Message-ID: <20130306120909.GU7544@kuru.dyndns-at-home.com> (raw)
In-Reply-To: <87d2vds8uf.fsf@gmail.com>
On Wed, Mar 06, 2013 at 12:52:24AM +0100, Nicolas Goaziou wrote:
> Suvayu Ali <fatkasuvayu+linux@gmail.com> writes:
>
> > I'm not sure what a \tableofcontents outside a frame would look like.
> > Can someone show an example?
>
> I think that the idea behind a frameless TOC is that you provide your
> own frame for it.
>
> It makes sense since #+TOC: allows to control accurately the location of
> your table of contents.
That makes a lot of sense. :)
> > I also had another thought; sometimes for long presentations, I use
> > something like this:
> >
> > \AtBeginSubsection[]{
[...]
> > }
> >
> > At the moment I put it in as one long LaTeX_HEADER line. But would it
> > be possible to leverage #+TOC: into having a similar effect? It might
> > then provide a greater degree of control where you want the toc frame to
> > appear.
>
> I think this kind of control should really belong to specific latex
> code.
>
> A TOC limited to current section sure sounds seducing, but I'm not sure
> how to achieve this in LaTeX.
I think you are right. I'll see if can find a nice way to do this in
LaTeX, I'll share if I find something.
Cheers,
--
Suvayu
Open source is the future. It sets us free.
next prev parent reply other threads:[~2013-03-06 12:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-05 13:11 [new exporter] #+TOC in beamer export Andreas Leha
2013-03-05 21:48 ` Nicolas Goaziou
2013-03-05 21:53 ` Andreas Leha
2013-03-05 22:35 ` Suvayu Ali
2013-03-05 23:52 ` Nicolas Goaziou
2013-03-06 12:09 ` Suvayu Ali [this message]
2013-03-06 18:21 ` Robert Eckl
2013-03-06 20:20 ` Andreas Leha
2013-03-06 22:40 ` Nicolas Goaziou
2013-03-06 23:30 ` Andreas Leha
2013-03-06 12:42 ` Nicolas Goaziou
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=20130306120909.GU7544@kuru.dyndns-at-home.com \
--to=fatkasuvayu+linux@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=n.goaziou@gmail.com \
/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).