From: Wolfgang Schuster <wolfgang.schuster.lists@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: LMTX MkIV difference in expansion
Date: Thu, 19 Nov 2020 21:41:00 +0100 [thread overview]
Message-ID: <44270398-0261-05e3-5b2b-94ac7c442301@gmail.com> (raw)
In-Reply-To: <7ca4ce38-e876-72d8-b64e-121e33823799@rik.users.panix.com>
Rik Kabel schrieb am 19.11.2020 um 21:20:
> Another LMTX/MkIV difference, this time with expansion:
>
> \define\Align{yes}
> \starttext
> \startalignment[\Align]
> This works with MkIV but fails with LMTX, complaining: {\tt
> tex error on line 3 in file G:/expand.mkvi: The file ended
> when scanning an argument.}
> \blank
> It works in both when \tex{def} or \tex{defineexpandable} is
> used instead of \tex{define}.
> \blank
> What changed?
> \stopalignment
> \stoptext
>
> It may well be that I have been abusing some laxity in MkIV and that
> LMTX is a bit stricter in what it accepts, but I would like to know if
> this is an expected difference.
You have to wait for Hans to get an answer but here is a minimal example.
\starttext
\protected\def\testparameter{test}
%\def\testparameter{test}
\def\test[#1]%
{\expandafter\let\expandafter\testargumentlist\csname#1\endcsname}
\test[\testparameter]
\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
___________________________________________________________________________________
next prev parent reply other threads:[~2020-11-19 20:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-19 20:20 Rik Kabel
2020-11-19 20:41 ` Wolfgang Schuster [this message]
2020-11-19 22:03 ` Hans Hagen
2020-11-19 23:18 ` Rik Kabel
2020-11-20 7:53 ` Hans Hagen
2020-11-21 15:05 ` Wolfgang Schuster
2020-11-21 15:25 ` Rik Kabel
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=44270398-0261-05e3-5b2b-94ac7c442301@gmail.com \
--to=wolfgang.schuster.lists@gmail.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).