From: Kevin Kenan <kevin@kevinkenan.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Space between heading and paragraph in a description
Date: Wed, 19 Feb 2020 07:22:17 -0800 [thread overview]
Message-ID: <BC3451F4-8F87-45EB-A58C-18C402BCC78B@kevinkenan.com> (raw)
In-Reply-To: <nycvar.YAK.7.77.849.2002182244320.4992@nqv-guvaxcnq>
[-- Attachment #1.1: Type: text/plain, Size: 521 bytes --]
> On Feb 18, 2020, at 7:45 PM, Aditya Mahajan <adityam@umich.edu> wrote:
>
> Add what you discovered to the wiki!
I did…after a fashion. Once I knew the answer, I was able to find a reference to it on the wiki. However, it was obscured because both \setupdescription and \setupdescriptions are listed and I was reading the entry for \setupdescriptions which doesn’t list stretch and shrink as parameters. I added a note to \setupdescriptions that references \setupdescription. Hopefully that will help.
-kk
[-- Attachment #1.2: Type: text/html, Size: 1381 bytes --]
[-- Attachment #2: Type: text/plain, Size: 493 bytes --]
___________________________________________________________________________________
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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2020-02-19 15:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-18 19:16 Kevin Kenan
2020-02-18 19:26 ` Wolfgang Schuster
2020-02-18 19:39 ` Kevin Kenan
2020-02-18 19:50 ` Wolfgang Schuster
2020-02-18 20:53 ` Kevin Kenan
2020-02-19 3:45 ` Aditya Mahajan
2020-02-19 15:22 ` Kevin Kenan [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=BC3451F4-8F87-45EB-A58C-18C402BCC78B@kevinkenan.com \
--to=kevin@kevinkenan.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).