Eggheads: is this for real?

TheRaven theraven at
Tue Feb 9 00:35:39 CST 1999

yeah yeah, everyone knows that.  The important part is the split 
command.  Which is possibly the most unclear command in the entire 8.0 tcl 


At 07:21 PM 2/6/00 , you wrote:
>Actually, utimer 10 [putserv "NOTICE [split $nick] [split $text]"] 
>wouldn't work. Since it's enclosed in brackets, it would first execute the 
>putserv command and take whatever value it returned, and insert it into 
>the 2nd argument in the utimer command. If you want to do something like 
>above you could either use the proc below or do:
>utimer 10 "putserv \"NOTICE \[split $nick\] \[split $text\]\""
>At 05:46 PM 2/6/99 -0800, you wrote:
>>Well, I'll be damned, it fucking works.
>>And here I thought my new rutimer was the only way it could be done :)
>>Thanks man.
>>proc rutimer {seconds command} {
>>   regsub -all {\[|\]|\$} $command {\\&} outtext
>>   return [utimer $seconds $outtext]
>>  Raven.
>>PS.  If I don't like the way the eggdrop tcl commands work, is there no 
>>way I can trap execution before or after *any* command and add my little 
>>proc in for manipulation?
>>At 06:20 AM 2/4/00 , you wrote:
>>>On Wed, 3 Feb 1999, TheRaven wrote:
>>> > Yeah, I agree with Ely on this one.  I had to write an unknown proc
>>> > replacement too - because of the inability of eggdrop's TCL 
>>> implementation
>>> > to handle utimers when their arguments are putserv statements with vars
>>> > that can potentially have []{} as their dynamic data.
>>> >
>>> > Another implementation of unknown procs :)
>>>Won't somthing like this do the same thing?
>>>utimer 10 [putserv "NOTICE [split $nick] [split $text]"]
>For unsubcribe information, visit:

More information about the Eggheads mailing list