On Tuesday, 30 October 2007 11:49 PM, Peter & Melodye Bowers <[EMAIL PROTECTED]> wrote: >> From: John Rankin [mailto:[EMAIL PROTECTED] >> Sent: Tuesday, October 30, 2007 4:58 AM >> >> On Monday, 29 October 2007 9:11 AM, Peter & Melodye Bowers >> <[EMAIL PROTECTED]> wrote: >> >The == operator seems to be working well in the simple case, but I >> believe >> >the "or" operator does not work with that operator. Any possibility of >> >getting that added in as well? >> > >> You are correct. I assume that what you mean is: >> >> field==value1|value2 >> >> exactly matches value1 or exactly matches value2. >> <snip> > >Yes, that's exactly what I meant -- exactly match value1 OR exactly match >value2.
Try installing the latest version -- field==value1|value2 should now work. > >Of course the operator ~= (a la perl) would allow one to match an anchored >regex OR an unanchored regex and have the maximum flexibility... Just a >suggestion... Is this solving a real problem or adding a gratuitous feature?? Of course, if you would like to send me the proposed code fragment and usage instructions, we can give it a try! JR -- John Rankin Affinity Limited T 64 4 495 3737 F 64 4 473 7991 021 RANKIN [EMAIL PROTECTED] www.affinity.co.nz _______________________________________________ pmwiki-users mailing list [email protected] http://www.pmichaud.com/mailman/listinfo/pmwiki-users
