Re: Escaping the Filter command's wildcards

At 6:30 PM -0700 5/22/2013, Peter Haworth wrote: I do find it strange that filter doesn't support full regexp syntax, seems like RunRev would have had to write special code instead of using standard regexp libraries which they use in other commands It was never supposed to be a regex command

Re: Escaping the Filter command's wildcards

Well it sounds like it will support full rgexp in the near future courtesy of Jan Schenkel and OSS. Pete lcSQL Software http://www.lcsql.com On Sat, May 25, 2013 at 4:46 PM, Jeanne A. E. DeVoto revolut...@jaedworks.com wrote: At 6:30 PM -0700 5/22/2013, Peter Haworth wrote: I do find it

Re: Escaping the Filter command's wildcards

at the same time. (La Rochefoucauld) - Original Message - From: Peter Haworth p...@lcsql.com To: How to use LiveCode use-livecode@lists.runrev.com Cc: Sent: Thursday, May 23, 2013 3:30 AM Subject: Re: Escaping the Filter command's wildcards I do find it strange that filter doesn't support

Re: Escaping the Filter command's wildcards

For those interested, I started the discussion on the engine contributors forum: http://forums.runrev.com/viewtopic.php?f=66t=15250 Cheers, Jan Schenkel.   = Quartam Reports PDF Library for LiveCode www.quartam.com = As we grow older, we grow both wiser and more foolish at the same

Re: Escaping the Filter command's wildcards

Thanks Jan. Pete lcSQL Software http://www.lcsql.com On Thu, May 23, 2013 at 10:10 AM, Jan Schenkel janschen...@yahoo.comwrote: For those interested, I started the discussion on the engine contributors forum: http://forums.runrev.com/viewtopic.php?f=66t=15250 Cheers, Jan Schenkel.

Re: Escaping the Filter command's wildcards

Hi Paul, This works fine for me: put replacetext(xxx?!xxx,[\?!],) -- xx What exactly is the problem you're having? Could you post some of the code that doesn't work for you? -- Best regards, Mark Schonewille Economy-x-Talk Consulting and Software Engineering Homepage:

Re: Escaping the Filter command's wildcards

Paul, I read your message three more times, and I think I should note that put replacetext(xxx?!xxx,\?,) works too: -- xxx!xxx in addition to put replacetext(xxx?!xxx,[\?!],) -- xx -- Best regards, Mark Schonewille Economy-x-Talk Consulting and Software Engineering Homepage:

Re: Escaping the Filter command's wildcards

I think there's been discussions on the list before about the filter command and the fact that it doesn't seem to support the full regexp syntax, only the specific functionality described in the dictionary Pete lcSQL Software http://www.lcsql.com On Wed, May 22, 2013 at 2:16 PM, Paul Dupuis

Re: Escaping the Filter command's wildcards

On 5/22/2013 5:37 PM, Mark Schonewille wrote: Hi Paul, This works fine for me: put replacetext(xxx?!xxx,[\?!],) -- xx What exactly is the problem you're having? Could you post some of the code that doesn't work for you? it is with the filter command not the replaceText function I

Re: Escaping the Filter command's wildcards

Hi Paul, I see what you mean. You weren't looking for a solution, just for more trouble :-) I tried several special characters and they can all be used to filter lines with the same workaround. Unfortunately, many of those special characters have no effect, because regex isn't fully

Re: Escaping the Filter command's wildcards

On 5/22/2013 8:32 PM, Mark Schonewille wrote: Hi Paul, I see what you mean. You weren't looking for a solution, just for more trouble :-) I tried several special characters and they can all be used to filter lines with the same workaround. Unfortunately, many of those special characters

Re: Escaping the Filter command's wildcards

I do find it strange that filter doesn't support full regexp syntax, seems like RunRev would have had to write special code instead of using standard regexp libraries which they use in other commands Shouldn't be too difficult to write a myFilter function that supports full regexp syntax using a