From: Taco Hoekwater <taco@elvenkind.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Removing Introduction section number
Date: Mon, 14 Jun 2010 09:54:30 +0200 [thread overview]
Message-ID: <4C15E036.7030204@elvenkind.com> (raw)
In-Reply-To: <201006140939.38581.alan.braslau@cea.fr>
Alan BRASLAU wrote:
> On Monday 14 June 2010 08:52:16 Taco Hoekwater wrote:
>> Vyatcheslav Yatskovsky wrote:
>>> ...or preventing startbodymatter from making new page.
>> \setupsectionblock[bodypart][page=no]
>>
>> or
>>
>> \setupsectionblock[frontpart][page=no]
>>
>> (I don't remember whether this is executed at the end
>> or the begin of the block).
>
> This is much more elegant than
> \subject{Whatever}
> \writelist[section]{}{Whatever}
> repeating "Whatever" twice.
>
> I will repeat here the suggestion, seconded by others, of parsing
> \section[number=no]{Whatever}
> to be used notably within \startbodypart...\stopbodypart
> Note that an unnumbered \section vs. \subject do not fill exactly the same
> need.
Actually, I almost never use \writetolist myself, but then I usually
have special sectioning commands (in larger documents):
\definehead[Usection][section]
\setuphead[Usection][number=no]
\Usection{...}
This could be wrapped in a macro if you want key=value parsing.
Best wishes,
Taco
___________________________________________________________________________________
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:[~2010-06-14 7:54 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-13 20:08 Vyatcheslav Yatskovsky
2010-06-14 6:52 ` Taco Hoekwater
2010-06-14 7:39 ` Alan BRASLAU
2010-06-14 7:54 ` Taco Hoekwater [this message]
2010-06-14 8:04 ` Alan BRASLAU
2010-06-14 8:14 ` Taco Hoekwater
2010-06-14 9:52 ` Hans Hagen
2010-06-14 10:14 ` Peter Münster
2010-06-14 10:21 ` Hans Hagen
2010-06-14 10:27 ` John Haltiwanger
2010-06-14 10:30 ` Alan BRASLAU
2010-06-14 11:17 ` Taco Hoekwater
2010-06-14 13:40 ` Alan BRASLAU
2010-06-14 13:55 ` Hans Hagen
2010-06-14 10:12 ` Hans Hagen
[not found] <mailman.1702.1276514035.4277.ntg-context@ntg.nl>
2010-06-14 11:18 ` Vyatcheslav Yatskovsky
[not found] <mailman.0.1276509602.1911.ntg-context@ntg.nl>
2010-06-14 10:54 ` Vyatcheslav Yatskovsky
[not found] <mailman.1480.1275862490.4277.ntg-context@ntg.nl>
2010-06-06 22:21 ` Vyatcheslav Yatskovsky
2010-06-06 22:23 ` Vyatcheslav Yatskovsky
2010-06-07 22:00 ` Rogutės Sparnuotos
[not found] <mailman.1477.1275853449.4277.ntg-context@ntg.nl>
2010-06-06 20:57 ` Vyatcheslav Yatskovsky
2010-06-06 21:15 ` Wolfgang Schuster
2010-06-13 20:03 ` Vyatcheslav Yatskovsky
2010-06-14 6:48 ` Taco Hoekwater
2010-06-14 12:27 ` Wolfgang Schuster
2010-06-14 12:30 ` Vyatcheslav Yatskovsky
2010-06-06 21:20 ` Yury G. Kudryashov
2010-06-06 21:46 ` Alan BRASLAU
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=4C15E036.7030204@elvenkind.com \
--to=taco@elvenkind.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).