Some text matching questions
|
Sep. 25, 2008, 03:02 PM
Post: #31
|
|||
|
|||
RE: Some text matching questions
(Sep. 25, 2008 03:56 AM)Vendettta Wrote: it's not apparent how the whole line should be expressed in a logical sequence. (!$SET(#=.))+{1,*} 1. Match ! 2. Set stack to . 3a. + says "Repeat 1 and 2". 3b. {1,*} says "Must match once, Match all." The 1 is needed because !+ would match ! or nothing. "space and", space? (Sep. 25, 2008 09:24 AM)lnminente Wrote: adding (^?) or $TST() later gives you the absolute security it will never match.What happens, if you use PrxNeverMatch(^?) and PrxNeverMatch is the last thing? |
|||
Sep. 25, 2008, 08:14 PM
Post: #32
|
|||
|
|||
RE: Some text matching questions
I think I've got it now. Thanks.
The space comment came from looking at your post in the white code view box. There appeared to be a space after the "." But after copying it and pasting into a text editor, the space disappears. Probably a monospace vs proportional font difference. |
|||
Sep. 26, 2008, 12:23 AM
Post: #33
|
|||
|
|||
RE: Some text matching questions
There is a really really really small posibility you could find prxnevermatch in a web, but the posibility is there. So to be sure about it will never match, it's better to use PrxNeverMatch(^?) or PrxNeverMatch$TST(), because (^?) or $TST() NEVER will match.
So, using PrxNeverMatch$TST() (or PrxFail$TST() like sidki does) you will have the faster speed and most security |
|||
Sep. 26, 2008, 04:50 AM
Post: #34
|
|||
|
|||
RE: Some text matching questions
(Sep. 26, 2008 12:23 AM)lnminente Wrote: because (^?) or $TST() NEVER will match. (^?) will match. I use it. Code: [Patterns] Testing: Code: prxnevermatch Result: Code: prxnevermatch (Sep. 26, 2008 12:23 AM)lnminente Wrote: There is a really really really small posibility you could find prxnevermatch in a web, but the posibility is there. I agree. |
|||
Sep. 26, 2008, 09:43 AM
Post: #35
|
|||
|
|||
RE: Some text matching questions
Wow! Thanks for that i wasn't know.
I was playing with your filter and if we set 13 as byte limit, then will match twice (gotcha gotcha) I take note, updating my filters |
|||
Oct. 27, 2008, 04:23 PM
Post: #36
|
|||
|
|||
RE: Some text matching questions
Could someone explain me why this happens?
Create a new filter and use this as matching code: ( <$SET(open=1)| >$SET(open=) )PrxFail$TST()| ?(^$TST(open=1)) Go to the test window and paste this: <font color="pink">BLA</font> <font color="pink">BLA</font> BLA BLA BLA <font color="pink">[table]</font> BLA BLA BLA <font color="pink">[table]</font> The result in the test windows is: <font color="pink"</font<font color="pink"</font<font color="pink"</font<font color="pink"</font It matched the > symbols!! To have this working i add (^>) before ?, but i would like to know why the first doesn't work. Maybe it was too fast and proxomitron had no time to set open=nothing? |
|||
Oct. 27, 2008, 04:55 PM
Post: #37
|
|||
|
|||
RE: Some text matching questions
Code: (^$TST(open=1)) When proxo sees the > character, var open is cleared. Then, $TST(open=1) evaluates to false. Not false = true Match! Afterwards, proxo matches every character till the next < character. z12 |
|||
Oct. 27, 2008, 06:14 PM
Post: #38
|
|||
|
|||
RE: Some text matching questions
Hi z12!
I was investigating some troubles with global variables (like Inside_Script and Inside_Link) using other filters with multi activated... Now i come mind refreshed and see it clear . I was not considering than the filter works exactly for the caracter wich goes after > than for the >. Many thanks for your help |
|||
Oct. 27, 2008, 07:06 PM
Post: #39
|
|||
|
|||
RE: Some text matching questions
Glad I could help.
z12 |
|||
Oct. 28, 2008, 01:11 AM
Post: #40
|
|||
|
|||
RE: Some text matching questions
I have to test some modifications i made... as soon as i get something i will tell you
|
|||
« Next Oldest | Next Newest »
|