From: Slawek Zak <zaks@prioris.mini.pw.edu.pl>
Subject: Missing table of contents
Date: 24 Dec 2000 01:12:47 +0100 [thread overview]
Message-ID: <87snnezngg.fsf@pf39.warszawa.sdi.tpnet.pl> (raw)
I've just installed latest beta and tried to compile following document:
\starttext
\completecontent
\chapter{A}
\section{One}
Aaa.
\chapter{B}
\section{One}
Aaa.
\stoptext
Maybe it's just to late, and I don't see some obvious error here, but shouldn't
table of contents be generated? It isn't - texexec runs once.
In the messages I get:
systems : begin file contents at line 1
title : - \headtext {\v!inhoud }
system : part,chapter,section,subsection,subsubsection,subsubsubsection
,subsubsubsubsection not found/processed
Merry Christmas and a Happy new Year to all of you, /S
next reply other threads:[~2000-12-24 0:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-24 0:12 Slawek Zak [this message]
2000-12-27 8:34 ` Hans Hagen
2000-12-27 12:09 ` Slawek Zak
2000-12-27 12:58 ` Hans Hagen
2000-12-27 14:24 ` Slawek Zak
2000-12-27 16:04 ` Taco Hoekwater
2000-12-27 20:07 ` Slawek Zak
2000-12-28 0:16 ` Hans Hagen
2000-12-29 12:34 ` Slawek Zak
2000-12-29 12:54 ` Hans Hagen
2000-12-29 13:44 ` Slawek Zak
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=87snnezngg.fsf@pf39.warszawa.sdi.tpnet.pl \
--to=zaks@prioris.mini.pw.edu.pl \
/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).