error and plain text with putnow

[pinkel]

I am using:

tcleggdrop_mcpsfuncs.tcl
tcleggdrop_mcps_sitesettings.ini

Everyting works fine if I use putserv and putquick.

But if I use putnow I am getting this error:

Tcl error [mcpshandlepubOK]: wrong # args: should be "info nick uhost hand chan text"

and the stuff is announced in plain text.

what could be the problem?

thanks

[DragnLord]

I am using:

tcleggdrop_mcpsfuncs.tcl
tcleggdrop_mcps_sitesettings.ini

Everyting works fine if I use putserv and putquick.

But if I use putnow I am getting this error:

Tcl error [mcpshandlepubOK]: wrong # args: should be "info nick uhost hand chan text"

and the stuff is announced in plain text.

what could be the problem?

thanks

What are you talking about?
"putnow" is not a standard eggdrop command, if you want help debugging you will need to post the procedure(s).

[pinkel]

I use this code to sent the text without buffering:

Code: Select all

proc putnow { a } {
  append a "\n"
  putdccraw 0 [string length $a] $a
}

I replace putserv/putquick with putnow.

To encrypt the text I use:

tcleggdrop_mcpsfuncs.tcl
tcleggdrop_mcps_sitesettings.ini

If I use putserv/putquick then al the text is encrypted, if I use putnow the text is announced in just plain text.

So my question was how can I solve this?

thanks

[metroid]

that error is not related to "putnow".

However, one of your scripts appears to be overwriting the TCL proc "info".

Which is the problem in your case, find out which script it is, and fix it

[DragnLord]

I doubt many here will be willing to dig up the scripts you have not posted just so they can help you.
Until you are willing to provide the information needed to fix your error(s), I suggest you use putquick so that it sends encrypted messages.

[speechles]

wrong # args: should be "info nick uhost hand chan text"

My bad, appears exactly as was said is the cause. This shows clearly that a procedure called 'info' exists which expects the arguments of: nick uhost hand chan text. Meaning it is more than likely triggered by a bind.

I was a little, erm.. stoned this morning and yeah...enough about that

[nml375]

Err, how does that code cause execution of [info] (and other instances of [])?
And how does the use of args alter that?

I would rather say that the error is someone creating a proc named info, which is an internal command name... As stated by Metroid earlier in this thread.