ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Wolfgang Schuster <schuster.wolfgang@googlemail.com>
To: "Idris Samawi Hamid ادريس سماوي حامد" <ishamid@colostate.edu>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>,
	Hans Hagen <pragma@wxs.nl>
Subject: Re: \definestructureresetset
Date: Thu, 10 Nov 2011 15:44:50 +0100	[thread overview]
Message-ID: <E272C20F-CAD5-4976-A05B-F8157D1AA2D1@googlemail.com> (raw)
In-Reply-To: <op.v4qg4rsppw6hmh@ishamid-pc>


Am 10.11.2011 um 14:59 schrieb Idris Samawi Hamid ادريس سماوي حامد:

> Dear gang,
> 
> I'm looking at strc*.mkiv trying to understand
> 
> \definestructureresetset[default][0,0,1,0][1]
> 
> etc.
> 
> The first argument would appear to control the continued-coupling between
> a higher and lower section. If 0, the lower section does not reset; if 1,
> the immediately lower section resets when the higher section increments up.
> 
> What is the second argument [1] for?

It’s the default argument for all section levels which are not listed in the second
argument, e.g. \subsubsection and below

To list all three argument we have:

1. “IDENTIFIER” or “SECTIONBLOCK:IDENTIFIER”
2. explicit values
3. default values

> ==========================
> \definestructureresetset[default][0,0,1,0][1] % this will not reset parts
> and subsections
> \setuphead[part][sectionresetset=default]
> \starttext
>      \placelist[chapter,section,subsection][criterium=all,width=3cm]
>      \part{first}  \chapter{alpha} \section{a} \section{b} \subsection{x}
> \subsection{y} \chapter{beta}
>      \part{second} \chapter{gamma} \section{a} \section{b} \subsection{x}
> \subsection{y} \chapter{delta}
> \stoptext
> ==========================
> 
> In this example -- from strc-def.mkiv with a small edit:
> 
> What is the diff between
> 
> \setuphead[part][sectionresetset=default]
> 
> and
> 
> \setuphead[part][sectionresetset=continue]
> 
> etc. Any clarifications appreciated and

“default” and “continue” are just names for a resetset but it’s a convention
that nearly all default sets have also the name “default”

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
___________________________________________________________________________________

  reply	other threads:[~2011-11-10 14:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-08 21:45 chapter please ignore part Idris Samawi Hamid ادريس   سماوي حامد
2011-11-09  5:24 ` Wolfgang Schuster
2011-11-10  3:59   ` Idris Samawi Hamid ادريس   سماوي حامد
2011-11-10 13:59   ` \definestructureresetset Idris Samawi Hamid ادريس   سماوي حامد
2011-11-10 14:44     ` Wolfgang Schuster [this message]
2011-11-10 13:59   ` \definestructureresetset Idris Samawi Hamid ادريس   سماوي حامد

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=E272C20F-CAD5-4976-A05B-F8157D1AA2D1@googlemail.com \
    --to=schuster.wolfgang@googlemail.com \
    --cc=ishamid@colostate.edu \
    --cc=ntg-context@ntg.nl \
    --cc=pragma@wxs.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).