From: Rasmus <rasmus@gmx.us>
To: emacs-orgmode@gnu.org
Subject: Re: Table of contents for just one section?
Date: Sun, 26 Oct 2014 11:53:35 +0100 [thread overview]
Message-ID: <87r3xvp0eo.fsf@gmx.us> (raw)
In-Reply-To: 87wq7uzwmm.fsf@nicolasgoaziou.fr
Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:
> Hello,
>
> "D. C. Toedt" <dc@toedt.com> writes:
>
>> I'd like to do sub-TOCs for individual sections and subsections.
>
> We could add a "local" keyword to TOC lines, e.g.,
>
> #+TOC: headlines 1 local
>
> would mean only top level children in current headline.
>
> This feature is trivial to add to ox-ascii, probably easy for ox-html or
> ox-odt, assuming someone can provide the expected code.
>
> Implementing it in ox-latex probably boils down to requiring another
> package (minitoc?).
I'm pretty sure you need an exernal package. titletoc or minitoc. At
least memoir seems to have issues with minitoc. KOMA-Script seems to
be ok. titletoc scores points for having a 24 pages manual, versus
800+ pages. Personally, I don't like the default style of minitoc.
> WDYT?
It's neat and I'd probably never use it.
—Rasmus
--
Hooray!
prev parent reply other threads:[~2014-10-26 10:54 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-16 3:50 Table of contents for just one section? D. C. Toedt
2014-10-20 13:41 ` Nicolas Goaziou
2014-10-20 14:06 ` D. C. Toedt
2014-10-26 8:15 ` Nicolas Goaziou
2014-10-26 11:03 ` D. C. Toedt
2015-03-16 22:35 ` D. C. Toedt
2015-03-16 22:47 ` Rasmus
2015-03-16 23:13 ` Thomas S. Dye
2014-10-26 11:32 ` Rasmus
2014-10-26 13:01 ` Nicolas Goaziou
2014-10-26 15:01 ` Rasmus
2014-10-26 15:10 ` Rasmus
2015-01-11 21:49 ` Nicolas Goaziou
2015-01-11 22:37 ` Rasmus
2015-01-12 8:38 ` Nicolas Goaziou
2015-01-12 10:45 ` Rasmus
2015-01-12 23:12 ` Nicolas Goaziou
2015-01-13 1:23 ` Rasmus
2015-01-13 9:30 ` Nicolas Goaziou
2015-01-13 10:21 ` Rasmus
2015-01-13 10:43 ` Nicolas Goaziou
2015-01-13 11:56 ` Rasmus
2015-01-13 15:36 ` Nicolas Goaziou
2014-10-26 10:53 ` Rasmus [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=87r3xvp0eo.fsf@gmx.us \
--to=rasmus@gmx.us \
--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).