ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Jim <zlists+context@jdvb.ca>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: [NTG-context] Re: Looking for itemize help
Date: Mon, 15 Jan 2024 16:11:46 -0400	[thread overview]
Message-ID: <ZaWRgiD19v8wedSL@x360.localdomain> (raw)
In-Reply-To: <8fd4127a-6978-422e-9111-72f9009a3fb1@fiee.net>

On Mon, Jan 15, 2024 at 20:33 (+0100), Henning Hraban Ramm wrote:

> Am 15.01.24 um 17:15 schrieb Jim:
>> "after" does the trick, but not in an automatic way.  I would like
>> something which automagically "does the right thing".

> With “automagically”, do you mean for all instances?

I hate to go out on a limb and say "all", but I mean that if there is text
"immediately" following the \stopitemize (i.e., no \par token or vertical
mode material before more text), then there is no white space following the
last \item.  But if there is a blank line following the last \item, there
will be vertical white space corresponding to the current \setupwhitespace
setting following the last item.

> \setupitemgroup[itemize][nowhite,after]

>>> Sorry, then you need "nowhite". Usually that’s synonymous to
>>> "packed,joineup", but apparently not if whitespace is active.

>> "Usually" is in the eye of the beholder.  ;-)

>> I would have thought that having non-zero whitespace between paragraphs is
>> common.  For example, Aditya's blog linked to above has whitespace between
>> paragraphs.  Are you suggesting that is uncommon, or (showing my
>> Context-noobness) is \setupwhitespace not the usual ConTeXt way to do this?

> Yes, it’s common, and \setupwhitespace is right.

OK, thanks for the confirmation.

> I just don’t remember all the setups in my many environments all the time.

>>> I added a few comments to
>>> https://wiki.contextgarden.net/Command/setupitemgroup
>>> Unfortunately, this is one of the areas where we have a plethora of options
>>> and no documentation about them.

>> Thanks for adding them.  I see you did not document the all-important (to
>> me) "after" (or "before") in the wiki.  Would you like to add that?  If
>> you don't have time right now, I'd be happy to do so.

> It’s there now.

Thanks, I have already seen them!

> I’m not sure about the options regarding width

I've done some more exploration about items in the last hour or so.  I'm
not sure I am yet ready to update the wiki (I am concerned that incomplete
information may be worse than no information), but if/when I feel
confident, I will add some information about some options.  (I guess the
implementation code is the current definitive documentation!)

Cheers.
                                Jim
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage  : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive  : https://github.com/contextgarden/context
wiki     : https://wiki.contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2024-01-15 20:15 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-15  0:42 [NTG-context] " Jim
2024-01-15  7:17 ` [NTG-context] " Henning Hraban Ramm
2024-01-15 14:36   ` Jim
2024-01-15 14:47     ` Aditya Mahajan
2024-01-15 16:15       ` Jim
2024-01-15 19:33         ` Henning Hraban Ramm
2024-01-15 20:11           ` Jim [this message]
2024-01-16  1:15         ` Bruce Horrocks
2024-01-16 14:39           ` Jim
2024-01-15 15:08     ` Henning Hraban Ramm
2024-01-15 15:51     ` [NTG-context] Re: [External] " Rogers, Michael K
2024-01-15 16:28       ` Jim
2024-01-15 16:39 ` [NTG-context] " Wolfgang Schuster
2024-01-15 18:26 Jim

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=ZaWRgiD19v8wedSL@x360.localdomain \
    --to=zlists+context@jdvb.ca \
    --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).