Re: Wildcard behavior different in SE and CI

[cld@xxxxxxxx]

From: Harry Binswanger 
> FYI, the following code, using ci/fn and the ascii-11 (the little male
> symbol) worked, to my surprise and delight:
>
> '%--_XYENCode_start--
> 'BXci/fn_~179"~Kjm;W";~[~179'`jm_"2.HIDE'.01-49,51-99"_'`q2;~[
> '`jm_;W;~['`jm_2.UNHIDE_'`q2;~[~179'Q2',*',
> '%--_XYENCode___end--

Well, I can't make heads or tails of that search string, but if it works, it works.

BTW, you don't absolutely need switch /FN and Ascii-11. You can put functions in SEarch and CHange
commands, just as they are; they're treated as strings. For example:

'BXch_|'JM2.blah|'JM2.bleah|'Q2

The only limitation is that if "Q2 " is in the SEarch string, you can't use Q2 to execute
the command; you need the alternate BX usage with parens, brackets or braces. For example, to CHange
"Q2 " to "XC ":

'BX(ch_|'Q2|'XC|)

--
Carl Distefano
cld@xxxxxxxx