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: goto(box) and setuplist questions
Date: Thu, 7 Aug 2008 09:48:16 +0200	[thread overview]
Message-ID: <115224fb0808070048y6c6b483cxb6ef604f7c9130cf@mail.gmail.com> (raw)
In-Reply-To: <326847810808061145o7e4471d0w8cf3af738edd6787@mail.gmail.com>

On Wed, Aug 6, 2008 at 8:45 PM, Alan Stone
<software.list.1es9s@gmail.com> wrote:
>>> The better way is to define you own list alternative.
>>>
>>> \define[3]\ChapterList
>>>  {\hbox
>>>     {\hbox to .5em{#1}\hskip.5em
>>>      \vtop{\hsize150pt\relax#2}%
>>>      \hfil#3}}
>>>
>>> \setuplist[chapter][alternative=command,command=\ChapterList]
>>
>> I'll try that...
>
> #1, #2, #3 being parameters which can be passed to \ChapterList, aka
> \ChapterList[#1,#2,#3]. Is that correct ?

Each lis entry has three argument:

#1: The section number
#2: The header text
#3: The page number

To define your own format for the list entry in the ToC you need a new
command with three argument like \def\MyCommand#1#2#3 and use it
in \setuplist with \setuplist[...][command=\MyCommand].

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


  parent reply	other threads:[~2008-08-07  7:48 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-04 11:06 Alan Stone
2008-08-04 12:23 ` Hans Hagen
2008-08-04 14:44   ` Alan Stone
2008-08-04 14:52     ` Wolfgang Schuster
2008-08-04 20:57       ` Alan Stone
2008-08-05  8:29         ` Wolfgang Schuster
2008-08-05 11:07           ` Alan Stone
2008-08-05 11:16             ` Wolfgang Schuster
2008-08-06  7:12               ` Alan Stone
2008-08-06  8:45                 ` Wolfgang Schuster
2008-08-06 10:16                   ` Alan Stone
2008-08-06 13:26                     ` Wolfgang Schuster
2008-08-06 14:15                       ` Alan Stone
2008-08-06 14:59                         ` Wolfgang Schuster
2008-08-06 16:07                           ` Alan Stone
2008-08-06 18:45                             ` Alan Stone
2008-08-07  6:26                               ` Wolfgang Schuster
2008-08-07  7:48                               ` Wolfgang Schuster [this message]
2008-08-07  6:24                             ` Wolfgang Schuster
2008-08-06 15:03                         ` Wolfgang Schuster
2008-08-06 15:13                           ` Alan Stone
2008-08-06 10:25                   ` Alan Stone
2008-08-06 11:03                     ` Wolfgang Schuster
2008-08-06 12:09                       ` Alan Stone

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=115224fb0808070048y6c6b483cxb6ef604f7c9130cf@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).