From: Berend de Boer <berend@pobox.com>
Cc: ntg-context@ntg.nl
Subject: Re: combined header texts
Date: Wed, 31 Jan 2001 06:17:47 +0100 [thread overview]
Message-ID: <3A779FFB.5070106@pobox.com> (raw)
In-Reply-To: <Pine.LNX.4.10.10101310048410.2175-100000@erde.kosmos.all>
Albrecht Kauffmann wrote:
> can someone, please, give me advice how to create headertexts, which
> should to content the chapternumber, the sectionnumber and the
> section? That is, e.g. "1.1 Einführung".
Here an example:
\setupfooter
[style=\sl]
\setupheader
[style=\sl]
\setupheadertexts
[chapter][section]
\setupfootertexts
[My document][]
See docs for valid contents of \setupheadertexts and \setupfootertexts.
Groetjes,
Berend. (-:
next prev parent reply other threads:[~2001-01-31 5:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-29 18:09 math fonts Albrecht Kauffmann
2001-01-30 11:09 ` Hans Hagen
2001-01-30 13:19 ` S2P development
2001-01-30 15:20 ` Hans Hagen
2001-01-30 23:57 ` combined header texts Albrecht Kauffmann
2001-01-31 5:17 ` Berend de Boer [this message]
2001-01-31 9:48 ` Hans Hagen
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=3A779FFB.5070106@pobox.com \
--to=berend@pobox.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).