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: No chapter prefixes in section numbers
Date: Fri, 3 Jun 2011 15:43:10 -0400	[thread overview]
Message-ID: <COL107-W31747F32E8CF09AA74AD01B27F0@phx.gbl> (raw)
In-Reply-To: <A4189C92-A902-4B4B-8B76-E281501F5BFE@googlemail.com>


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



Is there an exhaustive list of all the parameters the \setuphead function can take ?
Neither the 2011 ConTeXt Commands Manual nor the Wiki Command Reference page mention this one (sectionsegments).
Where can I find all the parameters one ConTeXt command can take ?
Thanks for enlightenment !


Mathieu



> From: schuster.wolfgang@googlemail.com
> Date: Thu, 2 Jun 2011 05:28:02 +0200
> To: ntg-context@ntg.nl
> Subject: Re: [NTG-context] No chapter prefixes in section numbers
> 
> 
> Am 02.06.2011 um 02:28 schrieb Aditya Mahajan:
> 
> > Hi,
> > 
> > I do not want chapter number to be prefixed in section and subsection numbers. Thus,
> > 
> > \starttext
> > \chapter{One}
> > \section{Two}
> > \subsection{Three}
> > \stoptext
> > 
> > should give:
> > 
> > 1 One
> > 1 Two
> > 1.1 Three
> > 
> > How to achieve that? I tried
> > 
> > \setuphead[section][prefixset=none]
> > 
> > but to no affect.
> 
> \setuphead[section]   [sectionsegments=section]
> \setuphead[subsection][sectionsegments=section:subsection]
> 
> Prefixes are used from commands which show the section numbers
> in front of their own number, e.g. floats or enumerations.
> 
> 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: 2617 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
___________________________________________________________________________________

  parent reply	other threads:[~2011-06-03 19:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-02  0:28 Aditya Mahajan
2011-06-02  3:28 ` Wolfgang Schuster
2011-06-03  4:40   ` Aditya Mahajan
2011-06-03 19:43   ` Mathieu DUPONT [this message]
2011-06-04 12:35     ` Wolfgang Schuster
2011-06-05 23:20       ` Mathieu Dupont
2011-06-06 10:44         ` Wolfgang Schuster
2011-06-19  8:02     ` Wolfgang Schuster
2011-06-19 23:42       ` Mathieu Dupont

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-W31747F32E8CF09AA74AD01B27F0@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).