tcl error in ex_cleanup

evildude · Post by **evildude** » Tue Sep 27, 2005 11:57 pm

Don't flame me too much but does anyone know why I get this error on the partyline of a *caugh* windrop?

Tcl error [ex_cleanup]: list element in quotes followed by ":" instead of space

demond · Post by **demond** » Wed Sep 28, 2005 12:27 am

because of applying list operations directly to string, which is incorrect (see FAQ section)

also, read sticky topics across forums and learn how to report problems

evildude · Post by **evildude** » Wed Sep 28, 2005 7:20 am

This is a problem I am seeing with the netbots. I didn't see any other posts about it so I didn't know if it was an issue with netbots or windrop. And thanks for your non-response.

De Kus · Post by **De Kus** » Wed Sep 28, 2005 7:36 am

try this:

Code: Select all

#open 'extras.tcl' from netbots
#search for on line ~61
  foreach file $files {
#replace with
  foreach file [split $files \n] {
#save, close and reload file/bot

if this works, we might want to report fix to slenox, if he doesnt read it anyway.
in case you get wired results now please post the return of '.tcl exec ls -a', because it seems your OS returns wired things in that case. If you use windrop, you should install "ls" for cygwin.

demond · Post by **demond** » Wed Sep 28, 2005 12:51 pm

evildude wrote:This is a problem I am seeing with the netbots. I didn't see any other posts about it so I didn't know if it was an issue with netbots or windrop. And thanks for your non-response.

oh, identifying the reason for your problem, as per your question, is a non-response to you? you demand more, although you can't be bothered with reading sticky topics and learning how to assist those who waste their time to help you?

heh

evildude · Post by **evildude** » Wed Sep 28, 2005 2:33 pm

Give me some of what you're smoking.

Post by **slennox** » Thu Sep 29, 2005 3:32 am

I haven't looked at the problem, but I suspect demond is correct and De Kus's fix is appropriate. Not planning any new releases of netbots.tcl at the moment.

If it weren't for the fact that it doesn't seem right to "cover up" my own bugs, I'd have deleted this thread, because the script name isn't mentioned in the topic.

evildude · Post by **evildude** » Thu Sep 29, 2005 7:09 am

Thank you, but I didn't know that it was a bug, I asked if anybody knew why the error occurred. I had an idea that it was located in extras.tcl but I wasn't sure if that was the script that was actually causing the error. I've been seeing that error for a very long time and have been checking here sometimes to see if any else was getting it. I did a forum search for several key words and nothing had been posted. I didn't know if it was being caused by some part of netbots, windrop, active tcl or what.

Alchera · Post by **Alchera** » Thu Sep 29, 2005 7:28 pm

@ evildude

In future you will follow the forum rules regarding posting, especially the "Subject" or risk having your posts removed.

demond wrote:also, read sticky topics across forums and learn how to report problems

demond · Post by **demond** » Thu Sep 29, 2005 11:04 pm

evildude wrote:Thank you, but I didn't know that it was a bug, I asked if anybody knew why the error occurred. I had an idea that it was located in extras.tcl but I wasn't sure if that was the script that was actually causing the error. I've been seeing that error for a very long time and have been checking here sometimes to see if any else was getting it. I did a forum search for several key words and nothing had been posted. I didn't know if it was being caused by some part of netbots, windrop, active tcl or what.

that's why I suggested to you reading sticky topics and learning how to report probs; if you had done that prior posting here, you would have learned that there is more to that error, and you can get a traceback by using .set errorInfo, which could have pointed out the culprit script