ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Bruce Horrocks <ntg@scorecrow.com>
To: ntg-context mailing list <ntg-context@ntg.nl>
Subject: [NTG-context] Re: documentation: parameters of \setuplist
Date: Wed, 24 Apr 2024 00:00:11 +0100	[thread overview]
Message-ID: <002BA696-6029-40D5-A26E-8CF14254EB41@scorecrow.com> (raw)
In-Reply-To: <5238b4f3-2301-446c-9d1b-a1d6a5a78d79@fiee.net>



> On 23 Apr 2024, at 20:43, Henning Hraban Ramm <texml@fiee.net> wrote:
> 
> Am 22.04.24 um 18:09 schrieb Henning Hraban Ramm:
>> I tried to complete https://wiki.contextgarden.net/Command/setuplist, but I don’t understand all parameters.
>> Can anyone explain these please:
>> * state (start stop): what does this en-/disable? collecting entries?
>> * label (yes no none Name): language dependent labels? as a prefix or what?
>> * location (none, here): disable placement? when makes this sense?
>> * symbol (one two three none default): where is this used?
> 
> One solved, still 4 to go… Please, anyone who used these?

In the source there is a comment relating to location:


%D Regular list entries are bound to a specific location in order to get the right
%D pagenumber etc.\ associated. When pushing something inbetween (in mkiv) it ends
%D up directtly in the list. This is the default because otherwise users will wonder
%D why spacing might get messed up (due to an unseen but present node). It is
%D possible to force a location by explicitly setting \type {location} to \type
%D {here}.
%D
%D Another way to force a certain order is to set the \type {order} variable when
%D placing a list. The \type {command} option only pushes commands into the right
%D order, and \type {all} orders all entries (which might be too much). In this case
%D no specific location is needed with the inbetween method. Maybe additional
%D mechanisms show up some day. See \type {inbetween-001.tex} for an example.

I don't really understand what capability the comment is referring to let alone be able to create an example demonstrating the difference.

—
Bruce Horrocks
Hampshire, UK

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

  parent reply	other threads:[~2024-04-24 10:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-22 16:09 [NTG-context] " Henning Hraban Ramm
2024-04-22 16:30 ` [NTG-context] " Duncan Hothersall
2024-04-22 18:46   ` Henning Hraban Ramm
2024-04-23 19:43 ` Henning Hraban Ramm
2024-04-23 21:14   ` Wolfgang Schuster
2024-04-24 17:34     ` Henning Hraban Ramm
2024-04-23 23:00   ` Bruce Horrocks [this message]
2024-04-24 17:31     ` Henning Hraban Ramm

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=002BA696-6029-40D5-A26E-8CF14254EB41@scorecrow.com \
    --to=ntg@scorecrow.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).