There has been discussions going on about what things should be loaded
by epic at startup.
Traditionally, ircII has loaded
2.8script
sets up a bunch of /ons for /trace, /links, and /stats,
as well as a /topic and /invite alias.
extensions
creates the 'umode', 'dmesg', and 'dquery' aliases, and
loads the 'newaway' script which implements a
/set show_away_once work-alike
version
sets /set client_information
local
This is configurable by the user
and optionally 'basical' but not by default
EPIC loads
builtins
an epic4 compatability script that implements a bunch of
aliases that were built in commands in epic4.
2.8script
the "smart join" and "smart leave" alises,
an /on send_public compat hook,
the /trace, /links, and /stats handlers from ircII.
Some compat stuff for efnet/ircnet stuff.
local
This is configurable by the user
and basical
This is a compat script with ircI, with a bunch of shorthand
aliases that people just assume are part of epic.
It also sets the first window's name to ircII,
It also sets up some compat /on set's.
There are three proposals that have been made:
1) Create a new command line option that supresses loading 'global'
2) Make the -q command line option suppress loading 'global'
3) Don't load 'basical' from 'global', because ircII doesn't do it
And other proposals can probably be made. Which change should be made,
or should no change be made?
Jeremy
_______________________________________________
List mailing list
[EMAIL PROTECTED]
http://epicsol.org/mailman/listinfo/list
