|
DanteX Apprentice
Joined: 13 Aug 2007 Posts: 166
|
Posted: Tue Aug 28, 2007 2:28 pm
[2.01] searching for %0 in the help file |
When I do that search, I get very large ammount of topics. The problem is that 95% of them have nothing to do with it. So I don't know if it's the search function or what it is that doesn't work...
D |
|
|
|
Vijilante SubAdmin
Joined: 18 Nov 2001 Posts: 5182
|
Posted: Tue Aug 28, 2007 3:01 pm |
How were you preforming the search?
It is possible that the search is returning bad results, but if I remember right the only place that %0 is actually documented to work is with #MXPTRIG. %0 was never meant to actually be used in many of the places it was commonly used in zMud. It was originally enabled as a tintin compatibility, but was never documented. The lack of documentation for those circumstances where it works is because it was planned to be removed, and may not continuing working where and how it used to at anytime. |
|
_________________ The only good questions are the ones we have never answered before.
Search the Forums |
|
|
|
DanteX Apprentice
Joined: 13 Aug 2007 Posts: 166
|
Posted: Tue Aug 28, 2007 3:14 pm |
I go to the help files through the menu:
Help --> contents --> search for: %0 in the search field
Only that.
And it returns like 100 results or something. |
|
|
|
Fang Xianfu GURU
Joined: 26 Jan 2004 Posts: 5155 Location: United Kingdom
|
Posted: Tue Aug 28, 2007 3:32 pm |
It does return a lot of results that it shouldn't - and surprisingly, #mxptrig isn't one of them.
It's just that the search is returning results that it shouldn't in this case, and lots of them. |
|
|
|
Zugg MASTER
Joined: 25 Sep 2000 Posts: 23379 Location: Colorado, USA
|
Posted: Wed Aug 29, 2007 8:14 pm |
It's because the % character is used for functions, and the help file has to do some special stuff to match function topics that start with the % character.
Also, I think the other problem is that % is used for wildcard in SQL searches. CMUD is doing a "Description LIKE Pattern" where Pattern is your %0, and since % is the SQL wildcard character, this probably causes a bunch of extra matches.
I'll see if I can quote the % character when searching in a future version. |
|
|
|
|
|