From: "Tom" <Tom@tuxedo-press.com>
To: <ntg-context@ntg.nl>
Subject: Chapters not sowing up in ToC
Date: Mon, 14 Feb 2011 15:05:46 -0500 [thread overview]
Message-ID: <00e501cbcc82$91f26db0$b5d74910$@com> (raw)
When attempting to place only the chapter number on the first page of a
chapter, the chapters do not appear in the ToC & the ToC does not display.
Inserting #2 just before the last } in the definition for MyChapterCommand
causes the ToC to appear with chapter names although it and the chapters are
ugly.
Is it necessary to include chapter names at the beginning of chapters?
Perhaps this is intended because leaving chapter names off the beginning of
chapters would reduce the value of the ToC. Maybe ToCs are not desired in
such situations.
%insert #2 before last } to cause ToC to appear although
%very ugly
\def\MyChapterCommand#1#2% #1 is number, #2 is text
{\framed[frame=off]
{\vbox{\centerline{\headtext{chapter} #1}}}}
\setuphead[chapter]
[command=\MyChapterCommand,
header=empty,footer=chapter,page=mychapterpagebreak,
after={\blank[0.5in]},before={\blank[force,1.0in]}]
\starttext
\completecontent
\chapter{The First Chapter}
\input knuth
\chapter{The\\Second\\Chapter}
\input knuth
\stoptext
Tom Benjey
717-258-9733 voice
717-243-0074 fax
blog: www.TomBenjey.com
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next reply other threads:[~2011-02-14 20:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-14 20:05 Tom [this message]
2011-02-15 18:29 ` Wolfgang Schuster
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='00e501cbcc82$91f26db0$b5d74910$@com' \
--to=tom@tuxedo-press.com \
--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).