From: Peter Denisevich <pdenis2@attbi.com>
Subject: Table of Contents
Date: Fri, 16 Aug 2002 11:20:45 -0700 [thread overview]
Message-ID: <200208161120.45365.pdenis2@attbi.com> (raw)
Hi,
Like Kris Hermans, I can't get Context to generate a TOC. It was working with
the version on from TexLive 7 (installed from my TUG CDROM) but since
upgrading to Context 7.26.02 *AND* 8.15.02 it's broken. Minimal testfile:
\starttext
\placecontent
\chapter{First}
The quick red fox
\stoptext
Output:
<snip>
systems : begin file tt at line 1
! Undefined control sequence.
\ExpandCommand [#1][#2]->\dobeginoflist
\dostellijstin [#1][#2]\doutilities
...
\doplaatssamengesteldelijst ...gesteldelijst ][#2]
\stoplistreferences
{#1}\e...
<to be read again>
\chapter
l.3 \chapter
{First}
?
<snip>
BTW: This is the 1st time I've upgraded Context. What I did was:
1) unzip *.zip's into /usr/share/TeX/texmf-local (local tree _was_ previously
empty, so I downloaded _all_ the zips).
2) Copy ../perltk/* to /usr/share/TeX/texmf/context/perltk -- since TL7 has a
wrapper script in TEXHOME/bin/i386-linux that calls texexec.pl.
3) texhash, texexec --make, texhash
Is this approximately correct? In the future I would normally just upgrade
the fmt zip...
Regards,
Peter
--
"'I could have done it in a _much_ more complicated way', said the Red Queen,
immensely proud." -- quoted in Froberg, Intro. to Numerical Analysis, 1969.
next reply other threads:[~2002-08-16 18:20 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-16 18:20 Peter Denisevich [this message]
2002-08-18 12:11 ` Hans Hagen
[not found] <mailman.198.1457685375.2302.ntg-context@ntg.nl>
2016-03-11 9:32 ` Aidan Nichol
-- strict thread matches above, loose matches on Subject: below --
2016-03-10 20:45 Aidan Nichol
2016-03-10 22:48 ` Pablo Rodriguez
2016-03-12 7:29 ` Wolfgang Schuster
2015-09-28 12:27 table of contents Meer, Hans van der
2015-09-28 13:31 ` Wolfgang Schuster
2012-07-09 9:43 Meer, H. van der
2012-07-09 9:54 ` Wolfgang Schuster
2012-07-09 10:10 ` Wolfgang Schuster
2012-07-09 11:26 ` Aditya Mahajan
2012-04-04 12:20 Table " John Devereux
2012-04-05 7:14 ` John Devereux
2012-04-05 10:13 ` Willi Egger
2012-04-05 10:51 ` John Devereux
2011-05-23 17:18 Oliver Buerschaper
2011-05-23 17:27 ` Wolfgang Schuster
2010-04-29 10:12 table " Marius
2010-04-29 10:19 ` Wolfgang Schuster
2010-04-29 13:17 ` Marius
2010-04-29 20:17 ` Marius
2010-04-30 6:55 ` Wolfgang Schuster
2010-04-30 8:41 ` Marius
2010-04-30 11:13 ` Wolfgang Schuster
2010-03-21 9:18 Table " Alain Delmotte
2010-03-21 9:36 ` Mari Voipio
2010-03-21 9:37 ` Wolfgang Schuster
2010-03-21 10:39 ` Alain Delmotte
2003-06-18 17:44 Table of Contents John Culleton
2003-06-18 18:16 ` wmcclain
2003-06-18 18:25 ` Idris S Hamid
2003-06-18 19:38 ` John Culleton
2003-06-18 20:13 ` Idris S Hamid
2003-06-19 0:30 ` John Culleton
2003-06-19 17:08 ` John Culleton
2003-06-20 19:02 ` Idris S Hamid
[not found] ` <3EF349DF.88E61AE4@lamar.colostate.edu>
2003-06-21 15:03 ` John Culleton
2003-06-26 8:07 ` Hans Hagen
2003-06-26 16:33 ` John Culleton
2002-08-15 14:29 table of contents Kris Hermans
2002-08-15 16:11 ` Hans Hagen
2000-09-09 13:25 Table " Zeljko Vrba
2000-09-09 13:58 ` Berend de Boer
2000-09-10 7:36 ` Zeljko Vrba
2000-09-10 9:09 ` Mr. Wang Lei
2000-09-11 8:30 ` 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=200208161120.45365.pdenis2@attbi.com \
--to=pdenis2@attbi.com \
/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).