Matti Haack wrote:
> Thanks for the tip. I didn't expect, that my beloved Regexbudy would
> handle such a multiline regex (I just copied everything into it).
> But it showed me two errors, which could be easily removed.
It doesn't work for matching multiple regexp lines against sample text,
but
Kevin wrote:
> Matti Haack wrote:
>
>> during Startup, I get the message, that I have an 'regular expression
>> error' - I found that this is in my blackRe - how can I locate the
>> defective entry?
>> Is there a tool to test, or do I have to track it down by dividing
>> the file and st
Hello Chritian,
the regexes are not from the Default set and I am not shure, where I
got these Phrases originally from... So if you see no error message
during startup, your regexes should be fine.
Matti
>> But it showed me two errors, which could be easily removed.
>>
> Matti,
> please
> But it showed me two errors, which could be easily removed.
>
Matti,
please tell us what was wrong - specially if it was in the defaults.
Christian Rehkopf
-
This SF.net email is sponsored by: Splunk Inc.
Still grepp
Hello Kevin,
Thanks for the tip. I didn't expect, that my beloved Regexbudy would
handle such a multiline regex (I just copied everything into it).
But it showed me two errors, which could be easily removed.
Thank you
Matti
> Matti Haack wrote:
>> Hello,
>>
>> during Startup, I get the me
Matti Haack wrote:
> Hello,
>
> during Startup, I get the message, that I have an 'regular expression
> error' - I found that this is in my blackRe - how can I locate the
> defective entry?
> Is there a tool to test, or do I have to track it down by dividing
> the file and start it over?
Hello,
during Startup, I get the message, that I have an 'regular expression
error' - I found that this is in my blackRe - how can I locate the
defective entry?
Is there a tool to test, or do I have to track it down by dividing
the file and start it over?
Matti
-
Matti Haack - Hit Haa
