Message Auto-Reply

[wile]

bot will reply for a massage at the channel or nick
but i have an error which is

Tcl error [replychan]: wrong # args: should be "string option arg ?arg ...?"

here is the source problem
proc replychan {nick uhost hand chan rest} {
global botnick repchan
foreach targchan $repchan {if {[string match *[string tolower $targchan]* [string tolower $chan]]} {append reps "$chan $rest" ; replyuser $nick $uhost $hand $reps ; return 0}}
}

[Dereckson]

Please give a example of sentence that causes an error.

[caesar]

Place the *[string tolower $targchan]* in two "'s like: "*[string tolower $targchan]*" if you use *wildcards*

[stdragon]

I don't think the error is in that proc. It's probably in your "replyuser" function.

[wile]

hello mr. ceasar i tried your advice theres new error such as
[17:31] Tcl error [replychan]: wrong # args: should be "string match ?-nocase? pattern string"

[caesar]

Please do paste the code of the *replychan* proc.

[stdragon]

I'm sure caesar meant the replyuser proc, because replychan is already posted :)

[caesar]

Uhmm. yes, mea culpa. Btw, that *string match* thing should have some " in it..

[egghead]

bot will reply for a massage at the channel or nick
but i have an error which is

Tcl error [replychan]: wrong # args: should be "string option arg ?arg ...?"

here is the source problem
proc replychan {nick uhost hand chan rest} {
global botnick repchan
foreach targchan $repchan {if {[string match *[string tolower $targchan]* [string tolower $chan]]} {append reps "$chan $rest" ; replyuser $nick $uhost $hand $reps ; return 0}}
}

It feels like you are breaking the [string match] command across lines.
So, besides the comments/suggestions given above, make sure that you don't break the code across lines. Newlines, do matter.

WRONG:

Code: Select all

if { [string match *$targchan* \n
$chan]} { .... }

the \n indicates a newline

RIGHT:

Code: Select all

if { [string match *$targchan* $chan] } { \n
... }

Example of what may go wrong:

Code: Select all

if { [string match
hello world ]
} {
   puts "match"
} {
   puts "no match"
}

will result in:

wrong # args: should be "string match ?-nocase? pattern string"
while executing
"string match "
(file "test.tcl" line 1)

Another example

Code: Select all

if { [string 
match hello world ]
} {
   puts "match"
} {
   puts "no match"
}

will result in:

wrong # args: should be "string option arg ?arg ...?"
while executing
"string "
(file "test.tcl" line 1)

[egghead]

Uhmm. yes, mea culpa. Btw, that *string match* thing should have some " in it..

tclsh8.3
% set targchan foo
foo
% set chan #foobar
#foobar
% string match *$targchan* $chan
1
% puts *$targchan*
*foo*

[caesar]

try with two words like: foo bar .. and you will see a notable difference. if is one word only then is working, else.. see for yourself.

[egghead]

try with two words like: foo bar .. and you will see a notable difference. if is one word only then is working, else.. see for yourself.

First, I would assume that a channel name is a single word. But, if you insist...

tclsh8.3
% set targchan "foo bar"
foo bar
% set chan #foobar
#foobar
% string match *$targchan* $chan
0
% puts *$targchan*
*foo bar*

Now that I did see it for myself (as you asked), I wonder what your point is?

[caesar]

not like that silly.. like this: .tcl string match *foo* foo bar .. anyway, it realy dosen't matter.. I'm used to use the " to make the code look better and avoid any errors.

[egghead]

not like that silly.. like this: .tcl string match *foo* foo bar .. anyway, it realy dosen't matter.. I'm used to use the " to make the code look better and avoid any errors.

How would the code given by wile ever get to such a construction?

There are two string variables $targchan and $chan and they are compared to each other.

For sure, a command will fail if you don't use the proper syntax.