egghelp/eggheads community

!cmd pulled from txt file with timers

2008-06-20T13:52:47-04:00

The problem is probably with your text file.
me: !whatever "Test"
bot: says whatever to Test

me: !whatever Test"
bot: says whatever to Test"

I see it works if you use " " two rather than one, was hoping to strip on the accidental typo of one " that always gets me by the enter key lol

The script outputs a line from a text file when you type !whatever and the same if you type "!whatever test ...." the arguments you add after !whatever are never displayed in the output text (at least using the script I've written above). So if you have a modified version of the script, please paste it.

Statistics: Posted by Sir_Fz — Fri Jun 20, 2008 1:52 pm

!cmd pulled from txt file with timers

2008-06-20T09:04:12-04:00

Thanks

Statistics: Posted by cache — Fri Jun 20, 2008 9:04 am

!cmd pulled from txt file with timers

2008-06-20T00:05:28-04:00

.tcl set a "\"hello\""
Tcl: "hello"
.tcl set b [join $a]
Tcl: hello
.tcl set c $a
Tcl: "hello"

As I said above, [join] can help eradicate visibility of escapes, but the consequence is that it also removes other things (if they aren't over-escaped), such as double-quotes as evidenced above...

.tcl set a "\\\"hello\\\""
Tcl: \"hello\"
.tcl set b [join $a]
Tcl: "hello"
.tcl set c [join [join $a]]
Tcl: hello

basically, tclsh on the partyline.. enabling .tcl and .set allows combined usage and is nice.

If it's simply over-escaped text, as you can see above, [join] removes the visible escape and keeps intact the double-quotes. It is usually better to find the source of the over-escaping (which most times is simply the result of using [split] or "tcl special character" filters (which simulate [split] escape behavior) when it isn't required) and correcting it before attempting to repair the damage done after the fact. But for a quick fix, it's fine, and this is exactly why you should be using [join] to solve it.

Note: Your subject line '!cmd pulled from txt file with timers' indicates use of timers. Timers usually involve setting parameters to

elements and this has the same escape behavior as using [split] does. If you mean timer as in throttling a users use of commands (by checking elapsed time) then this has nothing really to do with timers, ignore this note. In both cases, [join] is the answer.
Code:
```
puthelp "privmsg $chan :[join [subst -nocommands $sexmsg]]" 
```
.tcl set a [join [subst -nocommands "hello $::botnick {"]]
Tcl error: unmatched open brace in list
.tcl set a [join [subst -nocommands "hello $::botnick{"]]
Tcl: hello sp33chy{
Unmatched open braces with spaces before them will crash this instantly. Afterall, we just want [join]s escape removing powers activated. [join] will see any unescaped curly bracings with leading spaces as list element fields and attempt to match and join them too, we don't want that.
Code:
```
puthelp "privmsg $chan :[join [string map { " \{" " \\\{" " \{" " \\\}" } [subst -nocommands $sexmsg]]]"
```
.tcl set a [join [string map { " \{" " \\\{" " \{" " \\\}" } [subst -nocommands "hello $::botnick {"]]]
Tcl: hello sp33chy {
.tcl set a [join [string map { " \{" " \\\{" " \{" " \\\}" } [subst -nocommands "hello $::botnick{"]]]
Tcl: hello sp33chy{
.tcl set a [join [string map { " \{" " \\\{" " \{" " \\\}" } [subst -nocommands "hello $::botnick"]]]
Tcl: hello sp33chy
This should work all combined, the string map will over-escape curly bracings if found (to stop [join] from trying to match list elements), then the [join] will remove all those over-escaped escapes, including the escapes on the curly bracings. The above is the code you should use...

...But to further everyone's knowledge, let's test those double-quotes.
.tcl set b "\""
Tcl: "
.tcl set a [join [string map { " \{" " \\\{" " \{" " \\\}" } [subst -nocommands "hello $::botnick $::b"]]]
Tcl error: unmatched open quote in list
.tcl set a [join [string map { " \{" " \\\{" " \{" " \\\}" } [subst -nocommands "hello $::botnick$::b"]]]
Tcl: hello sp33chy"
.tcl set a [join [string map { " \{" " \\\{" " \{" " \\\}" " \"" " \\\"" } [subst -nocommands "hello $::botnick { $::b"]]]
Tcl: hello sp33chy { "
Now we've got it, over-escaping any double-quotes with leading spaces as well should do it. In your case this should already be happening as witnessed by yourself and is the entire reason for this excercise. The below code is only to be useful to those reading this for some learning experience.
Code:
```
puthelp "privmsg $chan :[join [string map { " \{" " \\\{" " \{" " \\\}" " \"" " \\\"" } [subst -nocommands $sexmsg]]]"
```
And even still, this code is not perfect (certain combinations of special characters will cause tcl errors and will need placement into the string map escape sequences, this will happen often and unpredictably). It can never be entirely safe. It can only temporarily fix a bad situation and make it a little better. The best solution is finding where the escapes are being generated and put a stop to it there rather than attempt to fix it with additional code.

Statistics: Posted by speechles — Fri Jun 20, 2008 12:05 am

!cmd pulled from txt file with timers

2008-06-19T19:40:50-04:00

The problem is probably with your text file.

me: !whatever "Test"
bot: says whatever to Test

me: !whatever Test"
bot: says whatever to Test"

I see it works if you use " " two rather than one, was hoping to strip on the accidental typo of one " that always gets me by the enter key lol

Statistics: Posted by cache — Thu Jun 19, 2008 7:40 pm

!cmd pulled from txt file with timers

2008-06-19T15:21:23-04:00

Code:

 set sexmsg [join [randomline $sex]]

joining the line should eliminate the escape sequences, but might introduce other errors along the way.

Statistics: Posted by speechles — Thu Jun 19, 2008 3:21 pm

!cmd pulled from txt file with timers

2008-06-19T11:54:38-04:00

The problem is probably with your text file.

Statistics: Posted by Sir_Fz — Thu Jun 19, 2008 11:54 am

!cmd pulled from txt file with timers

2008-06-17T11:56:29-04:00

Code:

set sex "../data/whatever.txt"set usedcmd [expr {[unixtime]-60}]bind pub - !whatever cmdproc cmd {nick uhost hand chan arg} { global usedcmd sex if {[set t [expr {[unixtime]-$usedcmd}]] < 60} {  puthelp "privmsg $chan :You have to wait [expr {60-$t}] sec(s) before you can use this command."  return 0 } set usedcmd [unixtime] set sexmsg [randomline $sex] puthelp "privmsg $chan :[subst -nocommands $sexmsg]"}proc randomline f { set data [split [read [set file [open $f]]][close $file] \n] set position [rand [llength $data]] lindex $data $position}

I like this script, anyway it can be changed to work with !whatever "text"? The " character displays as does whatever to "text" adding those \ thingys.

Statistics: Posted by cache — Tue Jun 17, 2008 11:56 am

!cmd pulled from txt file with timers

2006-04-24T19:28:38-04:00

Thanks that worked

Statistics: Posted by cache — Mon Apr 24, 2006 7:28 pm

!cmd pulled from txt file with timers

2006-04-24T18:25:06-04:00

Code:

set sex "../data/whatever.txt"set usedcmd [expr {[unixtime]-60}]bind pub - !whatever cmdproc cmd {nick uhost hand chan arg} { global usedcmd sex if {[set t [expr {[unixtime]-$usedcmd}]] < 60} {  puthelp "privmsg $chan :You have to wait [expr {60-$t}] sec(s) before you can use this command."  return 0 } set usedcmd [unixtime] set sexmsg [randomline $sex] puthelp "privmsg $chan :[subst -nocommands $sexmsg]"}proc randomline f { set data [split [read [set file [open $f]]][close $file] \n] set position [rand [llength $data]] lindex $data $position}

Statistics: Posted by Sir_Fz — Mon Apr 24, 2006 6:25 pm

!cmd pulled from txt file with timers

2006-04-24T17:33:45-04:00

I gave this a try but I didn't get any errors

Code:

#######set sex "../data/whatever.txt" set usedcmd [unixtime] bind pub - !whatever cmdproc cmd {nick uhost hand chan arg} {  global usedcmd  global sex if {[unixtime]-$usedcmd < 60} {return 0}  set usedcmd [unixtime]  set sexmsg [string range [randomline $sex] 0 end]  puthelp "privmsg $chan :[subst -nocommands $sexmsg]"}proc randomline f {  set data [split [read [set file [open $f]]][close $file] \n]  set position [rand [llength $data]]  lindex $data $position }###########

Any idea what im doing wrong?

thanks

Statistics: Posted by cache — Mon Apr 24, 2006 5:33 pm

!cmd pulled from txt file with timers

2006-04-24T16:33:01-04:00

Code:

set usedcmd [unixtime]bind pub - !cmd cmdproc cmd {nick uhost hand chan arg} { global usedcmd if {[unixtime]-$usedcmd < 60} {return 0} set usedcmd [unixtime] # do your stuff here.}

Statistics: Posted by Sir_Fz — Mon Apr 24, 2006 4:33 pm

!cmd pulled from txt file with timers

2006-04-24T16:14:06-04:00

The way im looking at the script. it just stops that one person from re-using it right? Cause im trying to disable it for everyone at the same time till 60 secs is up...

Still trying to figure out how to combine the two scripts lol

thanks

Statistics: Posted by cache — Mon Apr 24, 2006 4:14 pm

!cmd pulled from txt file with timers

2006-04-23T18:16:14-04:00

Yeah, that's why I linked to the 2nd topic. I've implemented the cmd in 20 seconds there (you can change it to 60).

Statistics: Posted by Sir_Fz — Sun Apr 23, 2006 6:16 pm

!cmd pulled from txt file with timers

2006-04-23T15:41:14-04:00

Hi Sir,

I read those before posting but im trying to see if I can make it where you can only type !cmd once every 60secs instead of every 5 secs etc. Like if 60 secs wasn't up it would PM chatter and say 'Wait 60secs before reusing this cmd.'

thanks

Statistics: Posted by cache — Sun Apr 23, 2006 3:41 pm

!cmd pulled from txt file with timers

2006-04-23T04:45:03-04:00

See this and this (at the bottom).

Statistics: Posted by Sir_Fz — Sun Apr 23, 2006 4:45 am