On 10/31/2021 11:53 PM, Tomas Hala via ntg-context wrote:
Hi all,
I noticed that \doifinstring produces quite strange output if a command
follows immediately (or with any amount of spaces) after the substring
I am searching for:
-------------------------------------MWE
\starttext
\def\xxx{asdf \bf Z:\bf asdf} % strange
\def\xxx{asdf \bf Z: \bf asdf} % strange
\def\xxx{asdf \bf Z:: \bf asdf} % OK
\def\xxx{asdf \bf Z: text \bf asdf} % OK
\def\xxx{asdf \bf Z:{} \bf asdf} % OK
\doifinstring{Z:}{\xxx}{yes!}
\stoptext
----------------------------------OUTPUT
fbf@yes!
fbf@yes!
yes!
yes!
yes!
----------------------------------------
If I insert another character, text or {} between them
(with or without spaces), all is ok.
I would like to ask what is the cause of this behavior and how to
use the \doifinstring to prevent the "fbf@" on the output.
partial expansion of a protected macro where one doesn't expect it
before i patch i let wolfgang check it
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | 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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
