From: Pablo Rodriguez <oinos@gmx.es>
To: ntg-context@ntg.nl
Subject: Re: bug in \doifinset
Date: Thu, 28 May 2020 21:12:35 +0200 [thread overview]
Message-ID: <56c2d17c-71b3-9e63-5cc3-628acabdd6f6@gmx.es> (raw)
In-Reply-To: <e2c2af45-c645-540b-7ac8-fbd651a730a8@xs4all.nl>
On 5/28/20 12:23 AM, Hans Hagen wrote:
> On 5/27/2020 10:39 PM, Wolfgang Schuster wrote:
>> Pablo Rodriguez schrieb am 27.05.2020 um 22:31:
>>> [...]
>>> I think this may be a bug, since the sample above would only get "yes"
>>> with { i7}.
>>
>> No spaces are allowed in these lists. Older versions of the command
>> removed the spaces before the entries but the current version is stricter.
>
> we can use the old one, so only the raw variants then ignore the space;
> best to be downward compatible, even if this was never the formal spec
> (more a side effect)
Just in case it might be relevant.
I have been using \doifinsetelse for two months now.
Backwards compatibility is not an issue for me (after Luigi provided a
better approach to the issue)
Pablo
--
http://www.ousia.tk
___________________________________________________________________________________
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
___________________________________________________________________________________
prev parent reply other threads:[~2020-05-28 19:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-27 20:31 Pablo Rodriguez
2020-05-27 20:39 ` Wolfgang Schuster
2020-05-27 21:28 ` Pablo Rodriguez
2020-05-27 21:58 ` luigi scarso
2020-05-28 19:08 ` Pablo Rodriguez
2020-05-27 22:17 ` Wolfgang Schuster
2020-05-27 22:23 ` Hans Hagen
2020-05-28 19:12 ` Pablo Rodriguez [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=56c2d17c-71b3-9e63-5cc3-628acabdd6f6@gmx.es \
--to=oinos@gmx.es \
--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).