From: Steffen Wolfrum <context@st.estfiles.de>
Subject: subsubsubsection
Date: Sun, 31 Oct 2004 20:02:50 +0100 [thread overview]
Message-ID: <a06002002bdaae41d35d9@[62.134.77.50]> (raw)
Hi,
I have to typeset a document with 5 heading levels.
So I wanted to create a subsubsubsection (section-6).
But it doesn't work.
According to the manual I did it like that:
\definesection[section-6]
\setupsection[section-6][conversion=characters,previousnumber=no]
\definehead[LevelFive][section-6]
But these headings get numbers (like section-5)
and no entry in the TOC.
When I would define
\definehead[LevelFive][section-5]
then there is an entry in the TOC (but with the wrong counter)
Why does \definesection[section-6] not work (for me)?
Steffen
next reply other threads:[~2004-10-31 19:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-31 19:02 Steffen Wolfrum [this message]
2004-10-31 19:23 ` subsubsubsection Patrick Gundlach
2004-10-31 19:29 subsubsubsection Steffen Wolfrum
2004-10-31 21:20 ` subsubsubsection Patrick Gundlach
2004-11-01 11:08 subsubsubsection Steffen Wolfrum
2004-11-01 14:09 ` subsubsubsection Patrick Gundlach
2004-11-01 20:30 subsubsubsection Steffen Wolfrum
2004-11-01 20:53 ` subsubsubsection Patrick Gundlach
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='a06002002bdaae41d35d9@[62.134.77.50]' \
--to=context@st.estfiles.de \
--cc=ntg-context@ntg.nl \
/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.
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 NNTP newsgroup(s).