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: Sun, 5 Jun 2011 23:20:45 +0000	[thread overview]
Message-ID: <col107-w41B4067CDEC44878E43374B2610@phx.gbl> (raw)
In-Reply-To: <1B3DBA79-AD49-4C00-B72E-95E7A437F78B@googlemail.com>


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



Ok, thank you very much for the great work Wolfgang !
For now I guess I could look at the source code of a command to find out its properties (I am not familiar with TeX but maybe I can figure out a few things).
I tried http://source.contextgarden.net/ but I can't find out how to find the script of a command.
Can you help me out ?
Thanks !



Mathieu



From: schuster.wolfgang@googlemail.com
Date: Sat, 4 Jun 2011 14:35:04 +0200
To: ntg-context@ntg.nl
Subject: Re: [NTG-context] No chapter prefixes in section numbers




Am 03.06.2011 um 21:43 schrieb Mathieu DUPONT: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 ?
I’m working on a update for the command reference but it will stilltake some time unless i have looked in all source files. Even wheni have the list it won’t always help you because the reference isonly a list with all valid keys and values but it doesn’t explainthe meaning of them and how they need to be combined to havea certain output.
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: 3075 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-06-05 23:20 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
2011-06-04 12:35     ` Wolfgang Schuster
2011-06-05 23:20       ` Mathieu Dupont [this message]
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-w41B4067CDEC44878E43374B2610@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).