From: Tony Keating <keating@mech.uq.edu.au>
Subject: Generating a table of contents
Date: Tue, 19 Oct 1999 09:34:20 +1000 [thread overview]
Message-ID: <19991019093420.A31541@mars.rcode.com.au> (raw)
I'm trying to generate a table of contents without much luck. I think the
problem is due to the fact that I'm using \subject's rather than \section's
(though I could be wrong). I'm setting up the contents list with:
\definelist[subject]
\definelist[subsubject]
\definecombinedlist[contents][subject,subsubject]
Then after the \starttext, I use
\placecontents
to get the table of contents. But I get nothing in the output. texexec shows
the following error:
system : subject,subsubject not found/processed
It shows a similar error if I define the lists as chapter and section.
Anybody know what I'm doing wrong?
Tony.
--
Tony Keating <keating@mech.uq.edu.au> [http://www.mech.uq.edu.au/~tonyk]
PhD Student - Large Eddy Simulation of near-wall mass transfer
System Administrator - Physical Sciences and Engineering Computing Laboratory
Department of Mechanical Engineering, University of Queensland, AUSTRALIA
next reply other threads:[~1999-10-18 23:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-10-18 23:34 Tony Keating [this message]
1999-10-19 8:19 ` Hans Hagen
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=19991019093420.A31541@mars.rcode.com.au \
--to=keating@mech.uq.edu.au \
/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).