From: Taco Hoekwater <taco@elvenkind.com>
Subject: Re: setuphead and command
Date: Mon, 24 Jul 2006 12:13:15 +0200 [thread overview]
Message-ID: <44C49D3B.4000705@elvenkind.com> (raw)
In-Reply-To: <20060721214502.GA22061@shahin.dnsalias.com>
Hubertus Schmidt wrote:
> Hi all,
>
> It's supposed to look like
> ------------------------------------------------------------------------------
> def Define Variable
> ------------------------------------------------------------------------------
This is somewhat closer:
\def\CommandHeader#1%
{\framed[frame=off,bottomframe=on,
topframe=on,align=right,width=\textwidth]
{\makeline #1}}
\def\makeline#1#2%
{\hbox to 10em{\hskip14pt\type{#1}\hss}\index{#1}{\it #2}}
\definehead[Command][subject]
\setuphead[Command][deeptextcommand=\CommandHeader]
\starttext
\Command{{def}{Define Variable}}
\Command{{tsolve}{solve differential equation}}
\stoptext
Cheers, Taco
prev parent reply other threads:[~2006-07-24 10:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-21 21:45 Hubertus Schmidt
2006-07-24 10:13 ` Taco Hoekwater [this message]
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=44C49D3B.4000705@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).