TIP: Click on subject to list as thread! ANSI
echo: tub
to: Bob Jones
from: Mike Tripp
date: 2003-08-07 12:59:54
subject: Problems with NoARC in v1.11

Hello Bob.

05 Aug 03 22:15, Bob Jones wrote to Mike Tripp:

 BJ> SEND NORMAL NOARC 

 BJ> is a NO-OP in the route.cfg file....

An approach proposal:  Rather than working on making the above do something
which is already default behavior, how about taking care of the wildcard
statement that is contradicting the NORMAL NOARC default?  What if the
EXCEPT keyword was extended to support ROUTE and SEND statements the same
way it is for Gateroute, StripAttributes, TinySeenbys, etc?

Would a final catchall like:

SEND Normal World EXCEPT  

accomplish all of your objectives or are there others not on the table that
this wouldn't address?

I can certainly see some advantages in my own setup for something like:

ROUTE Crash 382/0 382/All EXCEPT 382/999

Whaddaya think?  It certainly wouldn't be culture-shock for us lifers, and
it would be transparent to existing setups until the user exercises the
option to implement. :)

.\\ike

--- GoldED 2.50+
* Origin: TechKnowledgy at Work (1:382/61.1)
SEEN-BY: 633/267 270
@PATH: 382/61 140/1 106/2000 633/267

SOURCE: echomail via fidonet.ozzmosis.com

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.