ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Aditya Mahajan <adityam@umich.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: question about \setupitemgroup
Date: Thu, 8 Dec 2016 19:27:15 -0500 (EST)	[thread overview]
Message-ID: <alpine.LNX.2.20.1612081925110.18245@ybpnyubfg.ybpnyqbznva> (raw)
In-Reply-To: <8485cd4b-01a9-5f8a-ff26-17494e2ac2c3@gmx.es>

[-- Attachment #1: Type: text/plain, Size: 1635 bytes --]

On Sun, 27 Nov 2016, Pablo Rodriguez wrote:

> I have the following sample:
>
>    \setupwhitespace[5em]
>    \startsetups[smallwspa]
>        \setupwhitespace[small]
>        \setupblank[small]
>    \stopsetups
>    \setupitemize[each][indenting=no, setups=smallwspa]


The setupitemize command does not accept the setups key.

>    \starttext
>    \input knuth
>
>    \startitemize
>    \dorecurse{5}{\item this is my item\par
>                        second paragraph\par
>                        third paragraph
>                        }
>    \stopitemize
>    \stoptext
>
> I’m trying to get a \blank[small] separation for paragraphs inside items
> and a \blank[medium] separation between items.
>
> I’m afraid that neither the after, inbetween and setups keys are working?
>
> How could I get these different separations for items and for paragraphs
> inside them?
>
> Many thanks for your help,

One workaround is to abuse the option key.

\setupwhitespace[5em]
\startsetups[smallwhitespace]
     \setupwhitespace[small]
     \setupblank[small]
\stopsetups
\unprotect
\setvalue{\??itemgroupkeyword SmallWhiteSpace}{\setups{smallwhitespace}}
\protect

\setupitemize[option=SmallWhiteSpace, indenting=no, inbetween={\blank[1cm]}]

\starttext
\input knuth

\startitemize
\dorecurse{5}{\item this is my item\par
                     second paragraph\par
                     third paragraph
                     }
\stopitemize
\stoptext

@Hans: Could you add a setups key to \startitemgroup? One could abuse the 
before key, but that is not always executed.

Aditya

[-- Attachment #2: Type: text/plain, Size: 492 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
___________________________________________________________________________________

  reply	other threads:[~2016-12-09  0:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-27 13:28 Pablo Rodriguez
2016-12-09  0:27 ` Aditya Mahajan [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-07-22 10:32 Question " Fabrice Couvreur
2016-07-22 10:47 ` Wolfgang Schuster
2016-07-22 11:06   ` Fabrice Couvreur
2016-07-22 14:12     ` Fabrice Couvreur
2016-07-23  8:28       ` Fabrice Couvreur
2016-07-23 16:41         ` Wolfgang Schuster
2016-07-24 10:28           ` Fabrice Couvreur
2016-07-27 10:53             ` Fabrice Couvreur

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=alpine.LNX.2.20.1612081925110.18245@ybpnyubfg.ybpnyqbznva \
    --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).