On Fri, Aug 22, 2014 at 4:32 PM, Thierry Douez <th.do...@gmail.com> wrote: > >> As I said, the problem was: </ >> needed to be: a \ backslash delimiting the / forward slash. > > Really? > > Mind you trying this simple one which works here > and without any backslash! > Typical (for me anyway) that worked fine so I thought I'd throw together a test stack and compare the two and NOW your original grep worked fine. So I thought maybe it was the message box as as I said, that's what I originally used to test your grep. But this time around it worked fine. So I'm left here scratching my head wondering what was different. Originally I tried a few <TAGS> and nothing worked until I inserted the backslash. > > Could you show me in the regular expression docs why > do we have to escape a slash? > So I looked into this and there is NO requirement to use \ to delimit the / char in PCRE grep. On further investigation it appears to be a limitation of the online grep tester which uses the / char to enclose the grep string so the server knows what you want to test.
So again, thank you for openning my eyes to group naming and branch reset, as to the rest I appologise for leading you up a garden path which I have no idea how I stumbled up :-( _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
