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