pub binding bug?

puffi · Post by **puffi** » Sat Jan 01, 2005 10:40 am

Hi, i know it sounds weird but as of 2005 all my pub-bindings work slightly different on my 1.6.17

pub bindings simply dont trigger when i use one or more arguments.

for example, i got a topic-script that tells the current topic with some extra information when a user writes .topic
now for ops of the channel (for real ops, not those who have the flag in the eggdrop, so the bind is for -|-) may edit the topic with + <sometext> or - <index>
all those bindings dont even work. i put a putlog-line to the very first line of the proc but the proc doesnt even get called.

the same behaviour for all other pub bindings

any ideas?

demond · Post by **demond** » Sat Jan 01, 2005 10:47 am

the very first idea that comes to mind would naturally and obviously be you post your script here

puffi · Post by **puffi** » Sat Jan 01, 2005 11:05 am

Code: Select all

bind pub -|- $thisbot(cmdchar)topic myown:pub_topic

proc myown:pub_topic {n uh h c a} {
  putlog "pub topic n: $n uh: $uh h: $h c: $c a: $a"
  return 1
}

the point simply is, that the scripts worked all before, like for 2 years or sth.

demond · Post by **demond** » Sat Jan 01, 2005 11:44 am

try ${thisbot(cmdchar)}topic

puffi · Post by **puffi** » Sat Jan 01, 2005 12:12 pm

doing

.topic
in a channal triggers it.

.topic testargone andtwo
doesnt

the binding itself is okay and did work without any problems. additionally, i didnt change any code...and few days ago .topic testargs did work fine

demond · Post by **demond** » Sat Jan 01, 2005 12:21 pm

so,

Code: Select all

bind pub -|- ${thisbot(cmdchar)}topic myown:pub_topic

is triggered by ".topic" and is not triggered by ".topic foo bar", assuming $thisbot(cmdchar) is "."?

puffi · Post by **puffi** » Sat Jan 01, 2005 12:39 pm

exactly. it doesnt matter if i replace the ${thisbot(cmdchar)}topic with .topic it shows the same behaviour.

i found this behaviour on 2 eggdrops with different scripts now, one running 6.16 and one running 6.17

i'm fairly sure 2 days ago the scripts worked just fine

demond · Post by **demond** » Sat Jan 01, 2005 12:56 pm

just for clarity: you haven't changed anything from 2 days ago - you haven't recompiled the bot and installed the new version and you haven't modified your scripts - yet the scripts won't work now as they worked 2 days ago, on the same bot?

puffi · Post by **puffi** » Sat Jan 01, 2005 12:59 pm

i didnt change anything in none of each eggdrop/* trees.
no new binaries, no new scripts, nothing.

just for clarity too..the two bots i could see this behaviour are on two different machines with different linux distributions, different scripts installed and they are even different versions.

it really looks like a year-2005-bug or sth o.O

demond · Post by **demond** » Sat Jan 01, 2005 1:27 pm

well, in such case I can see no other possible explanation than somehow changed shared libs - Tcl or otherwise

you can try to compile & install Tcl in your home dir and recompile & link the bot against it, not the system-wide libs