From: Pablo Rodriguez <oinos@gmx.es>
To: ntg-context@ntg.nl
Subject: Re: TOC- removing Contents 0
Date: Wed, 22 Apr 2020 15:06:25 +0200 [thread overview]
Message-ID: <8cdea6c0-b634-de0c-c6c0-5cae8bffe651@gmx.es> (raw)
In-Reply-To: <502646df-3697-3d69-bbd2-d1bc176c1c25@gmail.com>
On 4/22/20 2:44 AM, jbf wrote:
> A simple question, but I have not found an answer to it as yet:
>
> \completecontent does everything it is supposed to, including providing
> the title 'Contents' on the ToC page, but it also gives me as the first
> line in the ToC:
>
> Contents 0
>
> In fact the ToC appears on page 1, but regardless of the page it is
> appearing on, is there a way I can prevent that line from being produced
> as part of the ToC? I assume it would be something I need to do in the
> following setup:
>
> \setupcombinedlist
> [content]
> [list={chapter,section,title,subject,subsection}]
> \setuplist[chapter][style=normal,alternative=b, before=]
Hi Julian,
\completecontent is similar to simply use:
\title{Contents}
\placelist[content]
If you include title in \setupcombinedlist[content], you are requesting
that all titles are included in the TOC.
A workaround could be to create a special title command for the TOC,
such as in:
\definehead
[toctitle]
[title]
And then use the following instead of \completecontent:
\toctitle{Contents}
\placelist[content]
This should avoid the problem.
I hope ith helps,
Pablo
--
http://www.ousia.tk
___________________________________________________________________________________
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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2020-04-22 13:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-22 0:44 jbf
2020-04-22 6:20 ` Henning Hraban Ramm
2020-04-22 13:06 ` Pablo Rodriguez [this message]
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=8cdea6c0-b634-de0c-c6c0-5cae8bffe651@gmx.es \
--to=oinos@gmx.es \
--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).