From: Steffen Wolfrum <context@st.estfiles.de>
Subject: Re: Re: subsubsubsection
Date: Mon, 1 Nov 2004 12:08:00 +0100 [thread overview]
Message-ID: <a06002000bdabc815d404@[62.134.72.100]> (raw)
Patrick Gundlach <patrick@gundla.ch> wrote:
> Hello Steffen,
>
> > ... sure I have seen that subsubsubsection is already defined in core-sec.tex.
> > Then the numbering/charactering works fine ... BUT why does a heading that's mapped to it
> > just not appear in the TOC?
>
>
> Sorry, but I don't get it. Could you please try to make a small
> example file that shows us what you want to achieve?
>
>
> Patrick
Hah, it was just an forgotten entry in the darkest corner of my environment setup:
\definecombinedlist[content][... lots of entries ...][level=subsubsection]
^^^^^^^^^^^^^
I didn't remember this last option being set at the end of that unwrapped line.
Sorry for the trouble,
Steffen
next reply other threads:[~2004-11-01 11:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-01 11:08 Steffen Wolfrum [this message]
2004-11-01 14:09 ` 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='a06002000bdabc815d404@[62.134.72.100]' \
--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).