From: Marco Patzer <homerow@lavabit.com>
To: ntg-context@ntg.nl
Subject: Re: \chapter{} vs \startchapter..\stopchapter
Date: Thu, 8 Nov 2012 21:24:45 +0100 [thread overview]
Message-ID: <20121108212445.44d00af4@homerow> (raw)
In-Reply-To: <509C0CC3.8040200@meahan.net>
2012-11-08 Bill Meahan:
> I note there are two different ways of handling a chapter:
>
> The traditional \chapter{mytitle}
>
> \startchapter[title=mytitle, ownnumber=N ..]
> blah
> \stopchapter
>
> Is there any difference or advantage/disadvatage to using one method or
> the other?
With the start…stop syntax you can easily apply different options to
the individual structure elements or add additional information. The
\chapter syntax is less verbose but less flexible. But it has at
least one caveat that I know: The insidesection key of \setuphead
does not work.
> Other than the source code, is there anything that lists the keys for
> \startchapter somewhere?
Keys that I know about:
\startchapter[
label=...,
title=...,
marking=...,
list=...,
bookmark=...,
reference=... ]
\stopchapter
You can also add an additional pair of brackets with custom
settings:
\startchapter
[title={First chapter}]
[foo=bar]
\stopchapter
In the setups this information is accessible as:
\structureuservariable{foo}
> It's not documented in even the most recent command reference.
Welcome to ConTeXt :)
Be the first of your friends to add this information to the wiki.
Marco
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2012-11-08 20:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-08 19:49 Bill Meahan
2012-11-08 20:24 ` Marco Patzer [this message]
2012-11-09 8:05 ` luigi scarso
2012-11-09 18:12 ` Bill Meahan
2012-11-09 18:25 ` luigi scarso
2012-11-09 18:32 ` Bill Meahan
2012-11-09 18:44 ` luigi scarso
2012-11-09 20:57 ` Hans Hagen
2012-11-10 7:54 ` Alan BRASLAU
2012-11-10 15:10 ` Pontus Lurcock
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=20121108212445.44d00af4@homerow \
--to=homerow@lavabit.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).