ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Wolfgang Schuster" <schuster.wolfgang@googlemail.com>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: Re: Pesky list problem
Date: Mon, 22 Oct 2007 11:01:54 +0200	[thread overview]
Message-ID: <115224fb0710220201r1f9b2e23nafafd670780affcf@mail.gmail.com> (raw)
In-Reply-To: <200710201215.31542.john@wexfordpress.com>


[-- Attachment #1.1: Type: text/plain, Size: 1693 bytes --]

2007/10/20, John Culleton <john@wexfordpress.com>:
>
> On Friday 19 October 2007 05:24:14 pm john@wexfordpress.com wrote:
> > I tried building my own TOC as follows:
> > ...
> > \definelist[subject][alternative=a]
> > \definelist[subsubject][alternative=a]
> > \definelist[subsubsubject][alternative=a]
> > \definecombinedlist[foo]
> > [subject,subsubject,subsubsubject]
> > [level=subsubsubject,criterium=local]
> > \setupcombinedlist[foo]
> > \starttext
> > \title{Annotated Booklist}
> > ...
> > \placelist[foo]
> > \subject{Top Choices}
> >
> > \subsubject{General Publishing}
> > ....
> >
> > This set of commands stops with errors.
> >
> > What stupid thing did I do this time?
> > --
> > John Culleton
>
> Gave up on the above attempt, went back to the default chapter, section,
> subsection, subsubsection and suppressed numbering. Now I am where I
> wanted
> to be in the first place.
>
> When I set up interaction for subsubsection all the levels became
> interactive.
> Don't know why.   So for section and subsection I
> added "...interaction=pagenumber...". Since I had previously eliminated
> page
> numbers for these levels in the TOC that faked out the interaction.
>
> Now I need to add a thumbnail for the index so folks can get back there
> from
> any point. Will try the pdftex command.


Hi John,

it's a little bit too late but I found a way to put also subjects to the
table of contents, you can do this with a setup command in \setuphead.

\setuphead
   [subject]
   [incrementnumber=list]

This can help you in your next project if you want both a numbered and
a unnumbered section header in your document but both of them should
appear in the content list.

Wolfgang

[-- Attachment #1.2: Type: text/html, Size: 2354 bytes --]

[-- Attachment #2: Type: text/plain, Size: 487 bytes --]

___________________________________________________________________________________
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  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

      reply	other threads:[~2007-10-22  9:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-19 21:24 john
2007-10-20 12:11 ` Wolfgang Schuster
2007-10-20 16:15 ` John Culleton
2007-10-22  9:01   ` Wolfgang Schuster [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=115224fb0710220201r1f9b2e23nafafd670780affcf@mail.gmail.com \
    --to=schuster.wolfgang@googlemail.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).