ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Aditya Mahajan via ntg-context <ntg-context@ntg.nl>
To: Hans Hagen <j.hagen@xs4all.nl>
Cc: Aditya Mahajan <adityam@umich.edu>,
	mailing list for ConTeXt users <ntg-context@ntg.nl>,
	Wolfgang Schuster <schuster.wolfgang@googlemail.com>
Subject: Re: Spacing issue in itemize
Date: Fri, 14 Jan 2022 10:22:29 -0500 (EST)	[thread overview]
Message-ID: <nycvar.YAK.7.78.908.2201141020590.133457@nqv-guvaxcnq> (raw)
In-Reply-To: <96579ed4-0dcb-9ea5-174e-30cd5249d625@xs4all.nl>

On Fri, 14 Jan 2022, Hans Hagen wrote:

> > @Hans: Does it make sense to add a setups key to \setupitemize to keep such
> > changes local?
> % 0 = before/after
> % 1 = between unless before
> % 2 = between
> 
> \c_strc_itemgroups_spacing_mode\plustwo
> 
> The question then is: "what key" (we have c!inherit available) and "what
> values" (numbers ?) ...

alternative = (a|b|c) like placelist?

Aditya
___________________________________________________________________________________
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
___________________________________________________________________________________

      parent reply	other threads:[~2022-01-14 15:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-13 16:48 Gavin via ntg-context
2022-01-13 17:15 ` Aditya Mahajan via ntg-context
2022-01-13 21:32   ` Gavin via ntg-context
2022-01-14  8:09   ` Hans Hagen via ntg-context
2022-01-14 13:52     ` Gavin via ntg-context
2022-01-14 15:22     ` Aditya Mahajan via ntg-context [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=nycvar.YAK.7.78.908.2201141020590.133457@nqv-guvaxcnq \
    --to=ntg-context@ntg.nl \
    --cc=adityam@umich.edu \
    --cc=j.hagen@xs4all.nl \
    --cc=schuster.wolfgang@googlemail.com \
    /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).