ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Werner Hintze" <w.hintze@posteo.eu>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: Re: Chapter precis
Date: Thu, 28 Aug 2014 17:11:18 +0200	[thread overview]
Message-ID: <AAC86878-301D-476B-BBC3-414F8D1A4395@posteo.eu> (raw)
In-Reply-To: <B25B115D-6A48-4CA8-B61C-8E28B2791AB2@gmail.com>


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

The example works for me too. But the command doesn’t work in my file. 
I can’t find out why.



On 28 Aug 2014, at 16:46, Wolfgang Schuster wrote:

> Am 28.08.2014 um 16:17 schrieb Werner Hintze <w.hintze@posteo.eu>:
>
>> Some old fashioned novels have a chapter précis in the table of 
>> contents. In Latex exists the command \chapterprecis to put the text 
>> at the beginning of the chapter and in the able of contents. I 
>> thought, I can realize this in ConTeXt with
>>
>> \writebetweenlist[chapter]{XYZ}
>>
>> or with
>>
>> \weitetolist[chapter]{XYZ}
>>
>> But both produce only a fatal error. What’s wrong here?
>
>
> Hard to tell without a example which demonstrates the error because 
> the following works for me.
>
> \starttext
>
> \completecontent
>
> \chapter{This is a chapter}
>
> \writetolist[chapter]{}{This is a summary of the chapter with 
> \tex{writetolist}.}
>
> \writebetweenlist[chapter][location=here]{This is a summary of the 
> chapter with \tex{writebetweenlist}.}
>
> \chapter{This is another chapter}
>
> \stoptext
>
> Wolfgang
> ___________________________________________________________________________________
> 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
> ___________________________________________________________________________________

[-- Attachment #1.2: Type: text/html, Size: 2122 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:[~2014-08-28 15:11 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-28 14:17 Werner Hintze
2014-08-28 14:46 ` Wolfgang Schuster
2014-08-28 15:11   ` Werner Hintze [this message]
2014-08-28 15:13     ` Wolfgang Schuster
2014-08-28 15:17   ` Werner Hintze
2014-08-28 15:22     ` Wolfgang Schuster
2014-08-28 15:46       ` Werner Hintze
2014-08-28 15:57         ` Wolfgang Schuster
2014-08-28 16:17           ` Werner Hintze
2014-08-28 16:53             ` Wolfgang Schuster
2014-08-28 17:02               ` Werner Hintze
2014-08-30 13:42   ` Alan BRASLAU

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=AAC86878-301D-476B-BBC3-414F8D1A4395@posteo.eu \
    --to=w.hintze@posteo.eu \
    --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).