egghelp/eggheads community

bind pubm and '#' charactor issue

2004-07-10T03:03:24-04:00

Thank you, i changed the bind to take into account the channel name matching that comes first and eliminated the bug : )

Statistics: Posted by DayCuts — Sat Jul 10, 2004 3:03 am

bind pubm and '#' charactor issue

2004-07-08T15:40:53-04:00

The pubm binding matches against the channel name first, and because most channels contain a #, if you are wanting to use a # as well as part of your trigger you would want your binding to take the form of:

bind pubm - "% *#* % ?? *"

Of course, it would be more helpful if you were more specific in what exactly you wish for your users to type to trigger the event.

Statistics: Posted by strikelight — Thu Jul 08, 2004 3:40 pm

bind pubm and '#' charactor issue

2004-07-08T09:53:07-04:00

try escaping it with \ .ie \#

Statistics: Posted by greenbear — Thu Jul 08, 2004 9:53 am

bind pubm and '#' charactor issue

2004-07-08T09:46:30-04:00

I am using a bind with the hash (#) charactor in it, however this messed up the script, and somehow it is ignoring the part of the pubm that is before the # charactor (reversed commenting??)

Does the # charactor have some kind of special meaning in a bind pubm ?
Or does the special use of this charactor for script commenting cause it to be ignored in binds?

when i check the binds list with .binds, it correctly display the full bind such as 'pubm -|- *#* %s ?? %s* 5972 m:check'

I have tried removing the * from before the # and many other alternatives, it would be quite inefficient to have to use a * bind and run a regex on every line to check the proper syntax is being used.

The tcl documentation says nothing about a special meaning of the # in binds, and logically, if it was being treated as a comment then the bind would be triggering on the '*' part and not on the '* %s ?? %s*' (which is what it is doing)

Statistics: Posted by DayCuts — Thu Jul 08, 2004 9:46 am