ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Mathieu DUPONT <mathieudupont@hotmail.com>
To: ConTeXt <ntg-context@ntg.nl>
Subject: Re: \definehead \setuphead new type included in a list such as TOC
Date: Fri, 27 May 2011 10:08:11 -0400	[thread overview]
Message-ID: <col107-w46B447DCC1FFBEA3359EF5B2760@phx.gbl> (raw)
In-Reply-To: <F3A8B7C7-F8D9-4681-BFA1-E360275205AB@googlemail.com>


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



That was very useful.
Thanks again Wolfgang !



Mathieu



From: schuster.wolfgang@googlemail.com
Date: Thu, 26 May 2011 18:52:48 +0200
To: ntg-context@ntg.nl
Subject: Re: [NTG-context] \definehead \setuphead new type included in a	list such as TOC




Am 26.05.2011 um 18:15 schrieb Mathieu DUPONT:Hi,
In the following example, I define 2 new heads, and I want them to :
1- inherits from Title (or Chapter would be fine)2- show in the TOC3- not be counted (CHAPTER should be 1)
Is there an option I can put into \setuphead[Abstract][] so it gets included in the TOC ?That would be the easiest way of getting the three desired results.
Your own headings aren’t shown in the TOC because you use \completecontentwhich lists only the default numbered headings (\part, \chapter etc.)
There are different solution:
1. Replace \completecontent with the following
  \title{Contents}  \placelist[part,chapter,Abstract,Intro, section,...]
2. Redefine \completecontent (it’s explained in the big manual):
  \definecombinedlist[content][part,chapter,Abstract,Intro, section,...]
3. Create your own combinedlist:
  \definecombinedlist[mycontent][part,chapter,Abstract,Intro, section,...]
  \setupheadtext[mycontent=Contents]
  \starttext
  \completemycontent
  \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: 3442 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:[~2011-05-27 14:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-26 16:15 Mathieu DUPONT
2011-05-26 16:52 ` Wolfgang Schuster
2011-05-27 14:08   ` Mathieu DUPONT [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=col107-w46B447DCC1FFBEA3359EF5B2760@phx.gbl \
    --to=mathieudupont@hotmail.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).