egghelp/eggheads community

.match !@ban.* as a pub command. [SOLVED]

2007-02-26T15:24:37-04:00

Hmm, I'm guessing you meant in the foreach vars, I should've used

Nope. They would never cause an error because the variable names contain no special characters...

Code:

# the elements you append to the matches list are strings...lappend matches "[lindex $ban 0] [lindex $ban 5]"# ...but later you treat them like lists...foreach match $matches {    ... [lindex $match 0] ... [lindex $match 1]"}

To fix it, you could just lappend them both as separate elements and do

Code:

foreach {ban by} {...}

Code:

lappend matches [list [lindex $ban 0] [lindex $ban 5]]

and keep the rest like it is.

Statistics: Posted by user — Mon Feb 26, 2007 3:24 pm

.match !@ban.* as a pub command. [SOLVED]

2007-02-24T02:57:07-04:00

Thanks rosc2112 for this, it is exactly what i requested. I'll handle the rest

L.E.

Oh on more question ..i've tried the sendftp.tcl in the tcl archive but it doesn't work, i've searched the forum and i found another post with a dcc .sendfile command, tried that but same result ..

it just freezes, and i've tried it on 2 different servers.

Statistics: Posted by mavericku — Sat Feb 24, 2007 2:57 am

.match !@ban.* as a pub command. [SOLVED]

2007-02-23T15:34:51-04:00

1) You do case sensitive GLOB matching with IRC BAN as a pattern. (brackets have a special meaning in glob matching - case doesn't matter on irc)

i.e. [hi] will match either 'h' or 'i' and will not match '[hi]' (using string match).

Statistics: Posted by Sir_Fz — Fri Feb 23, 2007 3:34 pm

.match !@ban.* as a pub command. [SOLVED]

2007-02-23T15:29:04-04:00

Hmm, I'm guessing you meant in the foreach vars, I should've used like:

foreach

$mybans and foreach
- $matches.
  
  Is that what you mean?

Statistics: Posted by rosc2112 — Fri Feb 23, 2007 3:29 pm

.match !@ban.* as a pub command. [SOLVED]

2007-02-23T15:24:02-04:00

I tested this, it worked for me. YMMV
1) You do case sensitive GLOB matching with IRC BAN as a pattern. (brackets have a special meaning in glob matching - case doesn't matter on irc)
2) lindex used on strings is bad (and I know you know this )

I made the script the way it way requested. Mav knows enough to modify it if he wants it case-insensitive. And yeah I know it's not tcl-special char safe, but again, that's an exercise for Maverick

The results are lists aren't they? According to the [banlist] documentation, they are, and I used lappend to make the 'matches' list.

Statistics: Posted by rosc2112 — Fri Feb 23, 2007 3:24 pm

.match !@ban.* as a pub command. [SOLVED]

2007-02-23T09:06:29-04:00

I tested this, it worked for me. YMMV

Indeed It worked because your search pattern had the same case as your bans and the masks/handles did not contain any brackets and braces.
1) You do case sensitive GLOB matching with IRC BAN as a pattern. (brackets have a special meaning in glob matching - case doesn't matter on irc)
2) lindex used on strings is bad (and I know you know this )

Statistics: Posted by user — Fri Feb 23, 2007 9:06 am

.match !@ban.* as a pub command. [SOLVED]

2007-02-23T07:19:19-04:00

banlist [channel]
Returns: a list of global bans, or, if a channel is specified, a
list of channel-specific bans. Each entry is a sublist containing:
hostmask, comment, expiration timestamp, time added, last time
active, and creator. The three timestamps are in unixtime format.
Module: channels

Just filter the output of the banlist command to match your desired search mask. You know how to do the pub bind.
Something like:

Code:

bind pub - test proc:banlistproc proc:banlist {nick uhost hand chan text} {        set text [split $text];#always split input for safety :P        set mybans [banlist $chan];set matches ""        if {$mybans != ""} {                foreach ban $mybans {                        if {[lsearch -start -6 $ban $text] != -1} {                                lappend matches "[lindex $ban 0] [lindex $ban 5]"                        }                }                if {$matches != ""} {                        set i 0                        puthelp "PRIVMSG $chan :Matching bans found: [llength $matches]"                        foreach match $matches {                                incr i                                puthelp "PRIVMSG $chan :$i: [lindex $match 0] banned by [lindex $match 1]"                        }                } else {                        puthelp "PRIVMSG $chan :No bans matching [join $text] found on channel $chan."                }        } else {                puthelp "PRIVMSG $chan :No bans for channel $chan."        }}putlog "test.tcl loaded"#-I_Really_hate-Word-Wrap!-######################################################################################

I tested this, it worked for me. YMMV

Statistics: Posted by rosc2112 — Fri Feb 23, 2007 7:19 am

.match !@ban.* as a pub command. [SOLVED]

2007-02-24T03:07:20-04:00

Hi Guys,

as the title says i'd like your help .
I'd like to make a pub command that will search the bans list.

Example

.match *!*@172.21.*

Bot : Matching bans found 20, showing 5
bot : 1 . ban , banned by
bot : 2 . ban , banned by .
and so on.

Can you please lend me a hand here...

Mave

Statistics: Posted by mavericku — Fri Feb 23, 2007 4:56 am

egghelp/eggheads community

.match *!*@ban.* as a pub command. [SOLVED]

.match *!*@ban.* as a pub command. [SOLVED]

.match *!*@ban.* as a pub command. [SOLVED]

.match *!*@ban.* as a pub command. [SOLVED]

.match *!*@ban.* as a pub command. [SOLVED]

.match *!*@ban.* as a pub command. [SOLVED]

.match *!*@ban.* as a pub command. [SOLVED]

.match *!*@ban.* as a pub command. [SOLVED]

.match !@ban.* as a pub command. [SOLVED]

.match !@ban.* as a pub command. [SOLVED]

.match !@ban.* as a pub command. [SOLVED]

.match !@ban.* as a pub command. [SOLVED]

.match !@ban.* as a pub command. [SOLVED]

.match !@ban.* as a pub command. [SOLVED]

.match !@ban.* as a pub command. [SOLVED]

.match !@ban.* as a pub command. [SOLVED]