From: Hans Hagen <pragma@wxs.nl>
To: ntg-context@ntg.nl
Subject: Re: Unexpanded texdefinition produces “Undefined control sequence”
Date: Mon, 26 Aug 2013 12:10:51 +0200 [thread overview]
Message-ID: <521B29AB.6030606@wxs.nl> (raw)
In-Reply-To: <20130825190906.GU18239@homerow>
On 8/25/2013 9:09 PM, Marco Patzer wrote:
> On 2013–08–25 Wolfgang Schuster wrote:
>
>> The \starttexdefintion command looks for the “unexpanded” keyword
>> only when you apply also a argument but not when the arguments
>> are missing, i.e.
>
> Thanks for the explanation. Is that a bug or expected behaviour?
> I think it's odd that
>
> \unexpanded\def\foo{}
>
> and
>
> \starttexdefintion unexpanded foo
> \stoptexdefinition
>
> don't behave the same.
not a bug ... just not implemented (as it's pretty complex to do that
case efficiently at the tex end)
anyhow, as it seems to be needed, i redid the code and now we have:
\starttext
\starttexdefinition unexpanded test #1
[here #1]
\stoptexdefinition
\test{oeps}
\starttexdefinition global unexpanded test
[here test]
\stoptexdefinition
\test
\scratchcounter=123
\starttexdefinition global unexpanded expanded test #oeps
[here #oeps: \the\scratchcounter]
\stoptexdefinition
\test{oeps}
\stoptext
so, three optional qualifiers (also in that order), so you'd better
wikify it
Hans
-----------------------------------------------------------------
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
___________________________________________________________________________________
next prev parent reply other threads:[~2013-08-26 10:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-25 17:40 Marco Patzer
2013-08-25 18:56 ` Wolfgang Schuster
2013-08-25 19:09 ` Marco Patzer
2013-08-25 19:21 ` Wolfgang Schuster
2013-08-26 10:10 ` Hans Hagen [this message]
2013-08-26 23:17 ` Marco Patzer
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=521B29AB.6030606@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).