allowed regex in filter?

[Mike Bonner]

Ah k. The first message said "followed by at least one whitespace, hence my
confusion.  In the regex builder its working for me.  7.0.0 sortastable.

^..\S+ pulls c mykey for the first example. and mykey for the second.
adding a second space after the c nullifies the match as it should.

If you haven't messed with the regex builder, its very handy. (development
menu, plugins)  What version are you on?  Oh, and actually just realized I
haven't been trying it with filter.  BRB, gonna try.

With sample made up data, this is working for me (again, 7.0.0 stable)
filter lines of tField with  regex pattern "^..\S+"


On Thu, Jan 1, 2015 at 6:59 PM, Dr. Hawkins <dochawk at gmail.com> wrote:

> On Thu, Jan 1, 2015 at 4:59 PM, Mike Bonner <bonnmike at gmail.com> wrote:
>
> > It works just as well (as far as I can see) to type the space+ (or even
> > space*) or \s+.  Isn't the \S (capital) a negate match?   So it will
> match
> > anything but a whitespace char?  and lower case /s is match whitespace?
> >
>
> yes
>
> >
> > Just checked with the regex builder, and that is how its behaving. so use
> > \s+ rather than \S+ to match whitespace.
> >
>
> But I'm after non-whitespace :)
>
> The source pattern could be either a single character or space, followed by
> a space, followed by keyword I'm matching, another space, and one or more
> words, or just the keyword, followed by a spce, followed by one or more
> words.
>
> something like
>
> c mykey some sentence or another
>
> or
>
> mykey some sentence or another
>
> myKey needs to be at least three characters.
>
>
> --
> Dr. Richard E. Hawkins, Esq.
> (702) 508-8462
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>