Re: bug in \doifinset

[Wolfgang Schuster <wolfgang.schuster.lists@gmail.com>]

Pablo Rodriguez schrieb am 27.05.2020 um 23:28:
> On 5/27/20 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.
> 
> Many thanks for your reply, Wolfgang.
> 
> Without commas, lists are harder both to read and to write (at least, to
> me).

The \doifinset etc. commands are used for internal checks when a key 
accepts multiple values with the same result and none of the existing 
mechanism has a space after the comma. As a result of this I saw no 
problem with this limitation and without a more detailed example from 
you there is no reason to change this.

As Luigi already has shown there are ways to format your code in a way 
to create readable lists, below is another one but in the end it depends 
on your use case.

%%%% begin example
\starttext

\startsetups [check]

     \doifelseinset
         {
             i7
         }
         {
             i4,
             i5,
             i7,
         }
         {yes}
         {no}

\stopsetups

\directsetup{check}

\stoptext
%%%% end example

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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : http://contextgarden.net
___________________________________________________________________________________