From: Hans Hagen <pragma@wxs.nl>
Subject: decriptions
Date: Fri, 25 Jun 1999 13:39:30 +0200 [thread overview]
Message-ID: <37736A72.B9FB6AD1@wxs.nl> (raw)
Hi all and Wybo in particular,
I suppose this is what you want:
\setuplayout[width=100mm]
\definedescription
[description]
[location=hanging, % implemented recently
margin=standard,
headstyle=bold]
\definestartstop
[descriptions]
[before=\blank\startpacked,
after=\stoppacked\blank,
commands=\let\item\description]
\starttext
\dorecurse{10}{This one is for Wybo. }
\startdescriptions
\description {aap:} is a monkey, but much more can be told
about this animal;s for example they are hairy, mostly
brown or black and they resemble people a lot.
\item {noot:} is a vegetable; again there are many kinds
and you will get very fat if you eat lots of them.
\startdescription {this is a rather long item:}
it is not very interesting in itself, but gives me the
opportunity to tell you something about the description
environment: it is like an itemize, but with user-supplied
labels which are printed bold.
\stopdescription
\stopdescriptions
\dorecurse{10}{This one is for Wybo. }
\stoptext
I think it makes sense to add such latex counterparts to a specific
module m-latex or so. If needed, with some \begin \end alike
substitutes, like
\let\normalbegin\begin
\let\complexbegin\normalbegin
\def\simplebegin#1%
{\getvalue{start#1}\bgroup
\def\end##1{\egroup\getvalue{stop##1}}}
\definecomplexorsimple \begin
So, that one can now also say:
\begin{descriptions}
\item {aap:} is a monkey, but much more can be told
about this animal;s for example they are hairy, mostly
brown or black and they resemble people a lot.
\item {noot:} is a vegetable; again there are many kinds
and you will get very fat if you eat lots of them.
\item {this is a rather long item:} it is not very
interesting in itself, but gives me the opportunity to tell
you something about the description environment: it is like
an itemize, but with user-supplied labels which are printed
bold.
\end{descriptions}
But, keep in mind that \begin \end is used for different purposes in
context (block moves/reuse), although the definition given here is
supposed to take care of that (untested). So, consider this a last
resort.
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.nl
-----------------------------------------------------------------
next reply other threads:[~1999-06-25 11:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-06-25 11:39 Hans Hagen [this message]
1999-06-25 13:48 ` decriptions Taco Hoekwater
1999-06-25 11:53 ` decriptions Hans Hagen
1999-06-26 10:37 ` decriptions Wybo Dekker
1999-06-26 15:54 ` decriptions Hans Hagen
1999-06-26 21:09 ` decriptions Wybo Dekker
1999-06-26 23:03 ` decriptions 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=37736A72.B9FB6AD1@wxs.nl \
--to=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).