ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Henning Hraban Ramm <texml@fiee.net>
To: ntg-context@ntg.nl
Subject: [NTG-context] Re: documentation: parameters of \setuplist
Date: Wed, 24 Apr 2024 19:31:05 +0200	[thread overview]
Message-ID: <a57f7e61-98c6-41bf-945f-95dde89b2a00@fiee.net> (raw)
In-Reply-To: <002BA696-6029-40D5-A26E-8CF14254EB41@scorecrow.com>

Am 24.04.24 um 01:00 schrieb Bruce Horrocks:
> 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.

Thank you, so it looks like "location=here" is only used with 
\writebetweenlist to get the current page number.

Hraban
___________________________________________________________________________________
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-04-24 17:33 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
2024-04-24 17:31     ` Henning Hraban Ramm [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=a57f7e61-98c6-41bf-945f-95dde89b2a00@fiee.net \
    --to=texml@fiee.net \
    --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).