>And again...
>
>Now about ON message hooks.
>
>Some hooks, like alot of public_* hooks and channel_signoff
>are filtered agains current channel and sender channels,
>other hooks are common.
>
>Shouldn't it be more clean:
>either filtering are to be done by scripts or in ircclient core ?
>
>In last case there should be
>action_other, ctcp_other, etc_other -
> when channel (or general 'target') is not current,
>action_msg, ctcp_msg -
> when sender is not on channel it sends message to.
>and ever more:
>send_public_other, send_msg_other -
> when sending messages to not current channel/nick.
>
>?
>
>What 'policy' says about it ?
The special on hooks, such as /on public_other and so forth are a terrible
blight on ircII and exist strictly for backwards compatability (ie, this is
not a fight i want to pick right now). I *strenuously object* to adding
more of them. I also object to the removal of any legacy /on's for backwards
compatability's sake.
Jeremy
_______________________________________________
List mailing list
[EMAIL PROTECTED]
http://epicsol.org/mailman/listinfo/list
