Ok but what you're suggesting leads to my point... how do I define a "server-wallop"
window and an
"oper-wallop" window? I can't use the WALLOP level as it stands right now because
they'd both go to the
same window. I'm forced to either not use a window level and instead xecho to a window
of a particular
name (thereby defeating the purpose of window levels), or to make WALLOP be
"server-wallop" and use a
USERLOG level to be "oper-wallop".
As for splitting up the WALLOP hook, that isn't necessary and can be scripted simply
by looking at $1.
on wallop "*" {
xecho -l ${[$1] == [S] ? [WALLOP] : [OPERWALL]} ...
}
In this case, OPERWALL would be the "oper-wallop" window level.
On Wed, Mar 10, 2004 at 04:04:15PM -0600, Jeremy Nelson wrote:
> What Black wants is to have /on wallop or the WALLOP level to be split
> into two levels, one for server senders and one for non-server senders.
> This information is easily ascertained by $1 in /on wallop. My position
> is that it's really easy to do:
>
> /on wallop "% S *" { ... echo to server-wallop window ... }
> /on wallop "% \* *" { ... echo to oper-wallop window ... }
>
> But this is not necessarily a solution accepted by all stakeholders.
--
BlackJac
Foxlink EFNet Server Operator
You have reached the end of the Internet. Please turn back.
_______________________________________________
List mailing list
[EMAIL PROTECTED]
http://epicsol.org/mailman/listinfo/list
