From: Hans Hagen <pragma@wxs.nl>
To: ntg-context@ntg.nl
Subject: Re: Keyword order problem
Date: Fri, 06 Jun 2014 01:22:35 +0200 [thread overview]
Message-ID: <5390FBBB.5050107@wxs.nl> (raw)
In-Reply-To: <538E8A85.5080908@rik.users.panix.com>
On 6/4/2014 4:55 AM, Rik Kabel wrote:
> Keyword order appears to matter for the \blank command. The following
> example shows all orderings for the set {dimension, nowhite, samepage},
> some of which work and some of which do not. It also shows two orderings
> of {dimension, nowhite, samepage, disable}; one works and the other does
> not. This happens with TL13 as well as the 2014-06-01 beta.
>
> I can find no discussion of keyword ordering in the wiki, on the mailing
> list, or in the manuals.
The command
\enabletrackers[vspacing.spacing]
Gives some insight in the processing order. Samepage is an option that
changes the order (gravity) so it triggers a flush.
At some point I will redo part of that code (as it was written very
early in the mkiv/luatex development) but not today.
> Is this intentional, and if so, with what other commands are keywords
> similarly constrained? Whether or not this is intentional, can a
> developer please provide a suggested ordering to use until this is
> better documented or corrected? The order that keywords are presented in
> the wiki and in the reference manual are among those that fail.
>
> \starttext
> \subject{Without disable}
>
> 12pt,samepage,nowhite\blank[12pt,samepage,nowhite]
> works
>
> 12pt,nowhite,samepage\blank[12pt,nowhite,samepage]
> fails
>
> samepage,12pt,nowhite\blank[samepage,12pt,nowhite]
> fails
>
> samepage,nowhite,12pt\blank[samepage,nowhite,12pt]
> works
>
> nowhite,12pt,samepage\blank[nowhite,12pt,samepage]
> works
>
> nowhite,samepage,12pt\blank[nowhite,samepage,12pt]
> works
>
> \subject{With disable}
>
> 12pt,samepage,nowhite,disable\blank[12pt,samepage,nowhite,disable]
> works
>
> samepage,12pt,nowhite,disable\blank[samepage,12pt,nowhite,disable]
> fails
>
> \stoptext
>
>
>
> ___________________________________________________________________________________
> 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://tex.aanhet.net
> archive : http://foundry.supelec.fr/projects/contextrev/
> wiki : http://contextgarden.net
> ___________________________________________________________________________________
>
--
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
| www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2014-06-05 23:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-04 2:55 Rik Kabel
2014-06-05 23:22 ` Hans Hagen [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=5390FBBB.5050107@wxs.nl \
--to=pragma@wxs.nl \
--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).