But first, a few minor improvements; imatch

Before launching into 2.0.11 proper, I'm taking time out for a few minor enhancements:

• The chnmCmd now redisplays the Topic's content.
• Words like McBride, which should not be treated as WikiNames, can now be enclosed in {{double braces}}.
• All regex's used in the Ark have been extended to support "¦". Ex: "*BiLaf*¦*NoKas*" will now match strings containing either BiLaf or NoKas.

These changes have all been completed and will be included in the first release of 2.0.11.

There is also another change that I've discussed with Norm, but its a bit more than minor: imatch. (See below.) I expect imatch will be implemented in a separate version.

Currently what TagMatch does is add any matching topics to the list of visible topics. (I.E. They show up when you use the t command.) TagMatches of this kind are created using the match command from the cls display.

An alternate form of TagMatch will be created using the imatch command. This new kind of TagMatch will include any matching topics to the list of applicative topics. This is kind of like having wildcards in the pathname of an include, except that it works faster and uses global scope for matching.

Please remember when using tags that they are global across all cabinets. Use long names for tags. Topic names can be short because they are scoped based on structure, but tag names are not scoped and must be unique. (I've broken this rule in www.compstrm.org in several instances, unfortunately. Case in point, use of the desc tag on days in the calendar. Such tags are of limited use for tag matching.)