From: Wolfgang Schuster <schuster.wolfgang@googlemail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: \expandoneargafter?
Date: Tue, 15 Mar 2011 12:48:47 +0100 [thread overview]
Message-ID: <0E4690EA-F77C-4A09-825A-6530FD1F3349@gmail.com> (raw)
In-Reply-To: <706C68F4-A619-4457-86F0-EDADBFEF497E@uva.nl>
Am 15.03.2011 um 12:36 schrieb Hans van der Meer:
>
> On 15 mrt 2011, at 12:14, Wolfgang Schuster wrote:
>
>>
>> Am 15.03.2011 um 12:10 schrieb Hans van der Meer:
>>
>>> The ConTeXt system macro's used to contain a definition for \expandoneargafter (see Taco Hoekwater's article on this). What happened with it? It seems to have disappeared. A pity because I use it in my macros in several places.
>>>
>>> ! Undefined control sequence.
>>> l.3 \expandoneargafter
>>> \command{\abc}
>>>
>>> Someone who can help?
>>
>> Most of the command in context are now defined as \unexpanded
>> and because of this the command isn’t necessary anymore.
>>
>
> I see. But I used this for my own macros and now I cannot find the definition of \expandoneargafter.
>
> \def\comparenumericprefix#1#2{%
> % remember that #1 (\firstsortelement) has to be expanded first!
> \comparenumeric{\expandoneargafter\uptodelim{#1}}{\uptodelim{#2}}}
>
> Could it be that \expandoneargafter is defined as \expandafter\expandafter\expandafter?
syst-gen.mkii: \def\expandoneargafter #1{\@EA#1\@EA}
but now you can write
\unexpanded\def\uptodelim#1{#1}
\def\comparenumericprefix#1#2%
{\comparenumeric{\normalexpanded{\uptodelim{#1}}{...}}
and this will only expand “#1” but not \uptodelim.
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://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2011-03-15 11:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-15 11:10 \expandoneargafter? Hans van der Meer
2011-03-15 11:14 ` \expandoneargafter? Wolfgang Schuster
2011-03-15 11:36 ` \expandoneargafter? Hans van der Meer
2011-03-15 11:48 ` 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=0E4690EA-F77C-4A09-825A-6530FD1F3349@gmail.com \
--to=schuster.wolfgang@googlemail.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).