From: Wolfgang Schuster <wolfgang.schuster.lists@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
Jim <zlists+context@jdvb.ca>
Subject: [NTG-context] Re: Table of contents of unnumbered titles
Date: Sat, 9 Sep 2023 21:17:52 +0200 [thread overview]
Message-ID: <4422cb2f-9232-895b-f83c-ce1412931e91@gmail.com> (raw)
In-Reply-To: <ZPy1a6+4ZutNgb/K@x360.localdomain>
Jim schrieb am 09.09.2023 um 20:11:
> Hi,
>
> I am creating a document which is divided with the unnumbered levels
> (\title, \subject, ...).
>
> I would like a table of contents showing the names and page numbers,
> something like
>
> Blah blah blah 2
> Blah blah 4
> ...
>
> However, notwithstanding what I see in
> https://wiki.contextgarden.net/index.php?title=Titles&mobileaction=toggle_view_desktop#Unnumbered_titles_in_table_of_contents
> I can't get this to happen with unnumbered divisions.
>
> The above wiki reference says "the following might do that trick" but I
> think "might" is the keyword, since even the wiki doesn't show the "No
> number" entry in the \completecontent.
>
> I find it hard to imagine that I am the only Context user who wants to do
> this. Can anyone point me in the direction of a working example?
>
> And am I misinterpreting the wiki, or is the wiki page broken?
1. You have to change the value of the incrementnumber key for title,
subject etc.
2. You have to specify which sections are shown in the table of content
because by default only the numbered sections are listed.
%%%% begin example 1
\setuphead [title] [incrementnumber=list]
\setuphead [subject] [incrementnumber=list]
\setuphead [subsubject] [incrementnumber=list]
\definehead [contentstitle] [title]
\setupcombinedlist [content]
[list={chapter,title,section,subject,subsection,subsubject}]
\starttext
\completecontent
\title{Title}
\subject{Subject}
\subsubject{Subsubject}
\stoptext
%%%% end example 1
%%%% begin example 2
\setuphead [title] [incrementnumber=list]
\setuphead [subject] [incrementnumber=list]
\setuphead [subsubject] [incrementnumber=list]
\definehead [contentstitle] [title]
\starttext
\contentstitle{Contents}
\placelist[chapter,title,section,subject,subsection,subsubject]
\title{Title}
\subject{Subject}
\subsubject{Subsubject}
\stoptext
%%%% end example 2
Wolfgang
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2023-09-09 19:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-09 18:11 [NTG-context] " Jim
2023-09-09 19:17 ` Wolfgang Schuster [this message]
2023-09-09 20:34 ` [NTG-context] " Jim
2023-09-09 21:12 ` Wolfgang Schuster
2023-09-09 21:45 ` Jim
2023-09-09 19:38 ` Lutz Haseloff
2023-09-10 19:43 ` Jim
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=4422cb2f-9232-895b-f83c-ce1412931e91@gmail.com \
--to=wolfgang.schuster.lists@gmail.com \
--cc=ntg-context@ntg.nl \
--cc=zlists+context@jdvb.ca \
/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).