ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Matthew Claus" <matt@mclaus.com>
To: "Hans Hagen" <pragma@wxs.nl>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: contents empty?
Date: Wed, 19 Sep 2012 17:56:02 -0400 (EDT)	[thread overview]
Message-ID: <1348091762.927126875@apps.rackspace.com> (raw)
In-Reply-To: <505A328A.6020701@wxs.nl>


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


Fabulous - thank you very much.
 
I see now that criterium is often relevant to lists and registers.
 
I had searched for a good while before asking but clearly not for the right thing. I updated the \completecontent command on the wiki with two links to other pages that mention criterium with respect to the table of contents.
 
Thanks -
Matt
 
-----Original Message-----
From: "Hans Hagen" <pragma@wxs.nl>
Sent: Wednesday, September 19, 2012 5:00pm
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Cc: "Matthew Claus" <matt@mclaus.com>
Subject: Re: [NTG-context] contents empty?



On 19-9-2012 22:54, Matthew Claus wrote:
>
> Hi everyone,
>
> Using the 2012.09.16 minimals,
>
> \starttext
>
> \completecontent
> \chapter{Chapter One}
> \completecontent
 [criterium=text]


> \stoptext
>
> renders the first table of contents as expected but the second is empty.
>
> Should this work? I'm trying to place the contents as the final element of the frontmatter in a more complex document.
>
> Thank you -
> Matt
>
>
>
>
>
>
>
> ___________________________________________________________________________________
> 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
> ___________________________________________________________________________________
>


-- 

-----------------------------------------------------------------
 Hans Hagen | PRAGMA ADE
 Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
 tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
 | www.pragma-pod.nl
-----------------------------------------------------------------

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

[-- Attachment #2: Type: text/plain, Size: 485 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  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

      reply	other threads:[~2012-09-19 21:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-19 20:54 Matthew Claus
2012-09-19 21:00 ` Hans Hagen
2012-09-19 21:56   ` Matthew Claus [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=1348091762.927126875@apps.rackspace.com \
    --to=matt@mclaus.com \
    --cc=ntg-context@ntg.nl \
    --cc=pragma@wxs.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).