From: Aditya Mahajan <adityam@umich.edu>
Subject: Re: Description nesting
Date: Fri, 5 May 2006 19:40:27 -0400 (EDT) [thread overview]
Message-ID: <Pine.WNT.4.63.0605051939140.2656@nqvgln> (raw)
In-Reply-To: <ops82rxasn9niby6@localhost>
On Fri, 5 May 2006, nico wrote:
> Hello,
>
> Is there a way to nest some descriptions, where the nested descriptions
> respect the enclosing indentation?
>
> Funnily the wiki speaks about the subject
> (http://wiki.contextgarden.net/Description) but doesn't give any solution
> (btw, the given solution to have several paragraphs in a description looks
> obsolete since \start \stop works pretty well).
>
> Here is an example that I would like to see working:
>
> \definedescription[descr][
> headstyle=bold,style=normal,align=left,location=hanging,
> width=broad,margin=1cm]
Try,
\definedescription[descr][
headstyle=bold,style=normal,align=left,location=hanging,
width=broad,margin=2em, before=\doMySetup]
\def\doMySetup{
\setupdescriptions[descr]
[before=\startnarrower,after=\stopnarrower]}
>
> \setupwhitespace[medium]
>
> \starttext
>
> \startdescr{Para}
> This is a shorter item label, and some text that talks about it.
> The text is wrapped into a paragraph, with successive lines indented.
>
> This is another paragraph under the "Para" item.
>
> \startdescr{SubPara1}
> This is a shorter item label, and some text that talks about it.
> The text is wrapped into a paragraph, with successive lines indented.
> \stopdescr
> \startdescr{SubPara2}
> This is a shorter item label, and some text that talks about it.
> The text is wrapped into a paragraph, with successive lines indented.
> \stopdescr
> \stopdescr
>
> \stoptext
--
Aditya Mahajan, EECS Systems, University of Michigan
http://www.eecs.umich.edu/~adityam || Ph: 7342624008
next prev parent reply other threads:[~2006-05-05 23:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-05 11:09 nico
2006-05-05 23:40 ` Aditya Mahajan [this message]
2006-05-06 8:29 ` Hans Hagen
2006-05-06 22:30 ` nico
2006-05-06 8:30 ` Hans Hagen
2006-05-06 22:41 ` nico
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=Pine.WNT.4.63.0605051939140.2656@nqvgln \
--to=adityam@umich.edu \
--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).