From: Wolfgang Schuster <wolfgang.schuster.lists@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
Rik Kabel <ConTeXt@rik.users.panix.com>
Subject: Re: MkIV and LMTX difference in comma list expansion
Date: Mon, 26 Oct 2020 17:56:11 +0100 [thread overview]
Message-ID: <56ff8bbd-dc4c-64be-9df2-7fbe5f1967c1@gmail.com> (raw)
In-Reply-To: <44c73441-764f-5d6b-3d82-9b921e34a108@rik.users.panix.com>
Rik Kabel schrieb am 26.10.2020 um 17:34:
> Hello list,
>
> Another difference, perhaps the result of my lack of knowledge, but a
> difference.
>
> The following example produces different results for the fourth
> sequence, with the index being passed one item under MkIV and two items
> under LMTX.
>
> (The code is stripped out of a much more complex bit to show the issue.)
>
> [...]
>
> Did I misuse the comma list processing, or is this a bug?
Probably something we missed when the comma list processor was
rewritten. In the example below the braces are stripped when there is
only a single element (first and second list).
\def\CommalistEntry#1{\ruledhbox{\strut#1}}
\starttext
\dontleavehmode\processcommalist[{aaa}]\CommalistEntry
\dontleavehmode\processcommalist[{aaa,bbb}]\CommalistEntry
\dontleavehmode\processcommalist[{ccc,ddd},{eee,fff}]\CommalistEntry
\stoptext
Wolfgang
___________________________________________________________________________________
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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2020-10-26 16:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-26 16:34 Rik Kabel
2020-10-26 16:56 ` Wolfgang Schuster [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=56ff8bbd-dc4c-64be-9df2-7fbe5f1967c1@gmail.com \
--to=wolfgang.schuster.lists@gmail.com \
--cc=ConTeXt@rik.users.panix.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).