egghelp/eggheads community

weird

2003-04-10T07:41:22-04:00

ppslim's sugestion seems to be working fine, also the 'regexp'.. thank you.

Statistics: Posted by caesar — Thu Apr 10, 2003 7:41 am

weird

2003-04-10T07:33:50-04:00

There is no reason for this to happen. You may want to try the following instead of string match.

Code:

proc ctrl:filter {str} {regsub -all -- {\003[0-9]{0,2}(,[0-9]{0,2})?|\017|\037|\002|\026|\006|\007} $str "" str ; return $str}

That should be placed outside the proc.

Then use this instead of "string match"

Code:

if {[ctrl:filter $text] == $text} { return }

The above code was taken from No!Spam. It is used to filter out colour and control codes, so you can't insert it into text, to get around the spam filters.

The idea being. If the filtered text, is exactly the same to non-filtered text, it doesn't contain any characters.

If it isn't the same it does.

The filter above also removes a couple of other characters, including the anoying bell sound. They may be of use to you, but you can remove them. While it is a regexp, you can pretty much see the format it takes.

Statistics: Posted by ppslim — Thu Apr 10, 2003 7:33 am

weird

2003-04-10T07:33:58-04:00

use regexp

Code:

if {![regexp {\002|\003|\026|\037} $text]} {putserv "PRIVMSG $dest :return" return } putserv "PRIVMSG $dest :continue" }

I tested this

Code:

string match {*[\002]*} $text

on a bot and it always returns "0" if the text is bold or not, same thing with \003 \026 and \037

Statistics: Posted by Papillon — Thu Apr 10, 2003 7:32 am

weird

2003-04-10T07:22:45-04:00

Same thing as happend with the bold, happened to colour, underline and reverse. Same continue and same return..

Statistics: Posted by caesar — Thu Apr 10, 2003 7:22 am

weird

2003-04-10T07:16:00-04:00

Very very odd - have you tried removignt he \002 and leaving the rest in, to see what happens then?

Statistics: Posted by ppslim — Thu Apr 10, 2003 7:16 am

weird

2003-04-10T07:10:51-04:00

I've tested by removing one by one and finaly I've got to

Code:

proc action:colour {nick uhost hand dest keyword text} {if {![string match {*[\002]*} $text]} {putserv "PRIVMSG $dest :return"return } putserv "PRIVMSG $dest :continue"}

When is something with bold or without it he only says "return". After I've removed the "!" he only says "continue"..

Statistics: Posted by caesar — Thu Apr 10, 2003 7:10 am

weird

2003-04-10T06:52:05-04:00

Try removing one character from the match at a time, and confirm it is not the character codes.

Statistics: Posted by ppslim — Thu Apr 10, 2003 6:52 am

weird

2003-04-10T06:33:29-04:00

Thanks for the tip. It still acting weird, like I've just mentioned in my previous post.

Statistics: Posted by caesar — Thu Apr 10, 2003 6:33 am

weird

2003-04-10T06:28:15-04:00

Start using brackets then, sounds like a parsing mistake.

On top, reduce it to one string match using

Code:

if {![string match {*[\002\003\026\037]*} $text]} { putlog "return" return 0} putlog "continue"

The square brackets are a nice feature of string match, that allow a range of characters, and in genral mean "match any of these".

Statistics: Posted by ppslim — Thu Apr 10, 2003 6:28 am

weird

2003-04-10T06:19:13-04:00

Also, something more weird than I've ever seen. Replaced and removed like this:

Code:

  if {[string match "*\002*" $text] || [string match "*\003*" $text] || [string match "*\026*" $text] || [string match "*\037*" $text]} {putlog "return"return 1 }putlog "continue"

When I'm not using colors he "continues" and when I'm using them he *returns*.. Viceversa is not working, duno why.. Using colours he *returns* and when not using them he *returns* also..

Statistics: Posted by caesar — Thu Apr 10, 2003 6:19 am

weird

2003-04-10T06:12:22-04:00

I've added and replaced like this:

Code:

 if {![string match "*\002*" $text] || ![string match "*\003*" $text] || ![string match "*\026*" $text] || ![string match "*\037*" $text]} {putlog "return"return 0 }putlog "continue"

and eyther I've put return 0 or 1 I've seen only the return line not the continue one as should be, eyther I've userd *colors* or not.

Statistics: Posted by caesar — Thu Apr 10, 2003 6:12 am

weird

2003-04-10T06:07:26-04:00

Have your tried putting any putlog lines in.

That should allways be the first port of call.

Statistics: Posted by ppslim — Thu Apr 10, 2003 6:07 am

weird

2003-04-10T05:58:54-04:00

Code:

setudef flag colourbind ctcp * ACTION action:colourproc action:colour {nick uhost hand dest keyword text} {  if {$nick == $::botnick || ![channel get $dest colour] || [matchattr $hand of|fo $dest] || [isop $nick $dest]} { return }  if {![string match "*\002*" $text] || ![string match "*\003*" $text] || ![string match "*\026*" $text] || ![string match "*\037*" $text]} { return }  if {[string match "*#*" $text]} {    channel:spam $nick $uhost $hand $chan $text    return  }  if {[string match "*www.*" $text] || [string match "*http*" $text]} {    web:spam $nick $uhost $hand $chan $text    return  }  if {![botisop $dest]} {    set mask "*!*@[lindex [split $uhost @] 1]"    newchanban $dest $mask Colour "\0025\002 minutes ban for using colours within $dest" 5    return  }  set mask "*!*@[lindex [split $uhost @] 1]"  newchanban $dest $mask Colour "\0025\002 minutes ban for using colours within $dest" 5}

I have the channel +colour and it dosen't seem to be doing nothing. He stops after the no match of bold, colours, reverse and underline, duno why. Any sugestions, tips or something to make it more easier and to be working?

Statistics: Posted by caesar — Thu Apr 10, 2003 5:58 am