ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Otared Kavian <otared@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: local ToC after each chapter title
Date: Thu, 10 Jan 2019 15:21:46 +0100	[thread overview]
Message-ID: <8EEA04CC-3306-4129-9FB6-30B167B1E4C9@gmail.com> (raw)
In-Reply-To: <80E3FE35-8F39-41B1-9DFF-0A449FF608DD@fiee.net>

Hi Hraban,

Probably instead of

> \setuplist[chapter][
>  before=,
>  after={\placecombinedlist[content][criterium=local]},]

you wanted to say

\setuphead[chapter][
	before=,
	after={\placecombinedlist[content][criterium=local]}]

which gives the expected result without any problem…

Best regards: OK

> On 10 Jan 2019, at 14:34, Henning Hraban Ramm <texml@fiee.net> wrote:
> 
> Hello again,
> 
> in my current book project I need a local ToC after each chapter title.
> What’s wrong with my use of "after"?
> 
> The following example leads to a "TeX capacity exceeded" error:
> 
> \setupcombinedlist[content][%
>  list={chapter,section},]
> 
> \setuplist[chapter][
>  before=,
>  after={\placecombinedlist[content][criterium=local]},]
> 
> \starttext
> 
> \completecontent
> 
> \chapter{One}
> 
> \section{Knuth}
> \input knuth
> 
> \section{Tufte}
> \input tufte
> 
> \chapter{Two}
> 
> \section{Tufte 2}
> \input tufte
> 
> \chapter{Three}
> 
> \section{Zapf}
> \input zapf
> 
> \stoptext
> 
> (MkIV, version 2018.12.19 19:22)
> 
> 
> Greetlings, Hraban
> ---
> https://www.fiee.net
> http://wiki.contextgarden.net
> https://www.dreiviertelhaus.de
> GPG Key ID 1C9B22FD
> 
> ___________________________________________________________________________________
> 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
> ___________________________________________________________________________________

___________________________________________________________________________________
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
___________________________________________________________________________________

  reply	other threads:[~2019-01-10 14:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-10 13:34 Henning Hraban Ramm
2019-01-10 14:21 ` Otared Kavian [this message]
2019-01-10 15:46   ` Henning Hraban Ramm
  -- strict thread matches above, loose matches on Subject: below --
2012-07-18 13:41 Need help Shiv Shankar Dayal
2012-07-18 14:15 ` Local TOC after each chapter title (was: Re: Need help) Marco
2012-07-18 14:21   ` Wolfgang Schuster
2012-07-18 14:56     ` Marco
2012-07-19  7:26       ` Steffen Wolfrum
2012-07-19  8:41         ` Marco
2012-07-19  9:53           ` Local TOC after each chapter title Hans Hagen

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=8EEA04CC-3306-4129-9FB6-30B167B1E4C9@gmail.com \
    --to=otared@gmail.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).