emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Andreas Leha <andreas.leha@med.uni-goettingen.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: [new exporter] #+TOC in beamer export
Date: Wed, 06 Mar 2013 13:42:40 +0100	[thread overview]
Message-ID: <87vc94zolb.fsf@gmail.com> (raw)
In-Reply-To: <87lia17btl.fsf@med.uni-goettingen.de> (Andreas Leha's message of "Tue, 05 Mar 2013 22:53:42 +0100")

Hello,

Andreas Leha <andreas.leha@med.uni-goettingen.de> writes:

> Nicolas Goaziou <n.goaziou@gmail.com> writes:
>>
>> Andreas Leha <andreas.leha@med.uni-goettingen.de> writes:
>>
>>> from a recent thread I learned about #+TOC (there's always something new
>>> to learn about org mode).
>>>
>>> I'd like to use it in a beamer document.  Here I find it hard to use
>>> because it introduces its own frame.
>>>
>>> My question basically is:  How is this supposed to be used in a beamer
>>> doc?
>>> (And would it not be easier if it did not introduce its own frame?)
>>
>> It seems useful to keep frame around TOC generated from toc:t option.
>> But we could remove it from TOC generated from #+TOC keywords.
>>
>
> Thanks for taking this further.  Indeed, for the toc:t triggered TOC the
> frame is absolutely useful.
>
> So, I like your suggestion very much.

Applied. Thanks for the feedback.


Regards,

-- 
Nicolas Goaziou

      parent reply	other threads:[~2013-03-06 12:42 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
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 [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=87vc94zolb.fsf@gmail.com \
    --to=n.goaziou@gmail.com \
    --cc=andreas.leha@med.uni-goettingen.de \
    --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).