From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Difference in doifinset in MkII and MkIV
Date: Sat, 15 Oct 2011 10:49:02 +0200 [thread overview]
Message-ID: <4E9948FE.7080809@wxs.nl> (raw)
In-Reply-To: <alpine.LNX.2.02.1110142111250.14104@ybpnyubfg.ybpnyqbznva>
On 15-10-2011 03:13, Aditya Mahajan wrote:
> On Wed, 21 Sep 2011, Wolfgang Schuster wrote:
>> Am 21.09.2011 um 05:20 schrieb Aditya Mahajan:
>>
>>> The following works in MkIV but fails in MkIV:
>>>
>>> \unprotect
>>> \def\!!yesandon{yes,on}
>>> \doifinsetelse{yes}\!!yesandon
>>
>> \ExpandSecondAfter\doifinsetelse{yes}\!!yesandon
>>
>> It’s awkward but this how it works in MkII.
>
> \ExpandSecondAfter is MkII only, so I cannot use it for code that is to
> be used in both MkII and MkIV. So, I re-request my original proposal:
>
> in core-gen.mkii
>
> \def\p!doifinsetelse#1#2#3#4%
> {\donefalse
> \edef\!!stringa{#3}%
> \ifx\!!stringa\empty
> \else
> - \processcommalist[#4]\p!docheckiteminset
> + \processcommacommand[#4]\p!docheckiteminset
> \fi
> \ifdone\expandafter#1\else\expandafter#2\fi}
I cannot oversee the consequences of that.
Can't you wrap your call in
\expanded{\doifinsetelse{...}{...}} {} {}
this should work in both mk's
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:[~2011-10-15 8:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-21 3:20 Aditya Mahajan
2011-09-21 9:44 ` Wolfgang Schuster
2011-10-15 1:13 ` Aditya Mahajan
2011-10-15 8:49 ` Hans Hagen [this message]
2011-10-16 5:51 ` Aditya Mahajan
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=4E9948FE.7080809@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).