From: Rik Kabel <context@rik.users.panix.com>
To: ntg-context@ntg.nl
Subject: Re: (MkVI) Regression in named parameters, TL2013 to current
Date: Fri, 28 Feb 2014 22:39:12 -0500 [thread overview]
Message-ID: <53115660.7020901@rik.users.panix.com> (raw)
In-Reply-To: <531138AC.7070800@wxs.nl>
[-- Attachment #1.1: Type: text/plain, Size: 1739 bytes --]
On 2014-02-28 20:32, Hans Hagen wrote:
> On 3/1/2014 12:45 AM, Rik Kabel wrote:
>> % macros=mkvi
>>
>> \setupwhitespace[small]
>>
>> \def\ä<^>?z{Ä<^>?}
>
> only letters can make a \cs (not symbols)
Clearly this is not currently the case, although I would agree that it
should be. Is there any way to enforce it? The definition above
processes cleanly on TL2013 and the current beta. The log file shows
nothing.
And as I wrote in the first note, accepting non-letters (that is, other
than the basic unaccented Aa--Zz) makes delimited parameter patterns
difficult to use with Mark VI parameter names. Thus, we have the
situation described in the following example, when in fact all should
work without error (as I understand it, but perhaps \starttexdefinition
has other limits of which I am not aware).
% macros=mkvi
% Fails to compile with TL2013 and current beta
%\starttexdefinition Test #1¦#2.
% #1, #2!
%\stopdefinition
% Fails to compile with TL2013 and current beta
%\starttexdefinition Test #PARAM¦#ETER.
% #PARAM, #ETER!
%\stopdefinition
% Works with TL2013 and processes with errors on current beta
%\def\Test#PARAM¦#ETER.{#PARAM, #ETER!}
% Works with TL2013 and current beta
\def\Test#1¦#2.{#1, #2!}
\starttext
\Test No soap¦{radio}.
\stoptext
Perhaps these are two different problems, but they smell the same to me.
Finally, assuming that I am correct that
\starttexdefinition Test #PARAM¦#ETER.
should work, should
\starttexdefinition Test #PARAM ¦ #ETER .
work the same. That is, are spaces allowed for readability in the
definition pattern, or are they significant?
[-- Attachment #1.2: Type: text/html, Size: 2722 bytes --]
[-- Attachment #2: Type: text/plain, Size: 485 bytes --]
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2014-03-01 3:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-28 23:45 Rik Kabel
2014-03-01 1:32 ` Hans Hagen
2014-03-01 3:39 ` Rik Kabel [this message]
2014-03-01 9:59 ` Wolfgang Schuster
2014-03-01 14:40 ` 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=53115660.7020901@rik.users.panix.com \
--to=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).