EPIC4pre2

*** News 6/26/2000 -- New flag for /who, /WHO -DX -- dalnet who support
	The dalnet's WHO request takes some extra flags that can be used
	to conditionalize, or filter out, some of the data that might
	otherwise be returned.  You can now use these flags with /who -dx.
	The format looks something like this:

		/WHO -dx <dalnet options> <arguments to options>

	Note that this syntax is not the same as the -ux flag, which is used
	for the undernet who request.  This is because these flags are modeled
	after how the server expects to recieve the arguments.  The dalnet
	WHO request is   "WHO <options> <arguments>", whereas the undernet's
	is "WHO <target> <options> <arguments>".

*** News 6/26/2000 -- New flag for /who, /WHO -UX -- undernet who support
	The undernet's WHO request takes some weird extra flags and returns
	with weird reply numerics in a kind attempt to avoid breaking EPIC.
	However, EPIC is not tolerant of issuing WHO requests outside of the
	WHO queue, because it breaks userhost caching.  So if you want to use
	the extended undernet who request, you must specify the -ux option
	*AFTER* you specify the target and *BEFORE* you specify the special
	flags.  If you would please refer to the "who.stuff" document, this
	new option works something like this:

		/WHO <mask1> -ux <options> <mask2>

	<options> and <mask2> are passed as-is to the server without any 
	interpretation of any kind by EPIC.  The server will rrturn your 
	results in whatever way it pleases in a 354 numeric.  EPIC does 
	*ABSOLUTELY NOTHING WHATSOEVER* with this numeric reply, save offer
	it to you as an /on 354.  You are entirely on your own to parse the 
	results of /on 354.

	Only the "-u-i" and "-oper" options are compatable with the -ux flag.
	The use of any other options, including -line, -end, -host, and so on,
	will avail you not; they are silently ignored.

	All must immediately cease and desist using the awful /quote hack
	cited in the "who.stuff" document to get around EPIC's attempt to
	keep you from doing something that will likely crash the client.
	The use of that hack may result in EPIC crashing, and that is _NOT_
	my fault.

----- release break point -----

*** News 6/22/2000 -- New /window operator, /WINDOW HOLD_INTERVAL
	This operator overrides the value of /SET HOLD_INTERVAL for this
	window.

*** News 6/22/2000 -- New built in /set, /SET HOLD_INTERVAL
	This set controls how many lines must be added to your hold buffer
	before your status line is forcibly refreshed.  The default is 10,
	which is the traditional value.

*** News 6/22/2000 -- New built in function, $wordtoindex()
	Given a word number (counting from zero), this returns the index
	offset into the string (counting from zero) of the first character
	in that word.  This is useful if you need to find the start of a
	word that you are somewhere in the middle of.

*** News 6/22/2000 -- Numeric parameters available in /wait %cmd and /exec -end
	When you are inside a /wait %cmd {...} or /exec -end {...} body, the
	following numeric parameters are available:
		$0 - The name or number of the exec'd process
		$1 - The signal (if any) that killed the process
		$2 - The return code (if any) of the procss
	This is exactly the same as what you get inside /on exec_exit.

*** News 6/22/2000 -- New status bar expando, %{2}S
	This is the same as %S, except it does not truncate the server name
	at all.

*** News 6/22/2000 -- New built in function, $globi()
	$globi() is a case insensitive version of $glob().  It is identical
	otherwise.

*** News 6/22/2000 -- !ID channels on ircnet no longer formatted
	At the specific request of Kurt Roeckx (q@ping.be) and with the
	permission and blessing of Kaspar Landsberg (kasi), epic no longer
	will try to "pretty print" IRCNet's !ID channels.  They now appear
	as they come from the server.

*** News 6/22/2000 -- New on, /on channel_sync
	This was added as a birthday gift to Whitefang -- Happy 17th birthday!
	/ON CHANNEL_SYNC is thrown at the earliest possible moment that it
	is safe to perform _ALL_ channel-related built in functions (such
	as $userhost(), $chanops(), etc).  Before this /ON is thrown, some
	or all of the channel-related built in functions may return unuseful
	results.  The arguments are:
		$0 - The channel that is now synced
		$1 - The time (in fractional seconds) it took the channel
			to sync up.
		$2 - The server that this channel is on.

*** News 6/22/2000 -- New status bar expando, %{1}F
	%{1}F is exactly the same as %F (show notified windows with output
	since they have been hidden), except that it shows the window name
	instead of its refnum, if possible.

*** News 6/22/2000 -- New built in function, $loadinfo()
	$0 of the return value is the current line number in a file being
	loaded, and $1- is the name of the file being loaded.  This function
	only returns meaningful results *during a /load*.  Do not call this
	function outside of a script being /load'ed.

*** News 6/22/2000 -- /DCC LIST has more information now
	A transfer speed field has been added to the /dcc list output

*** News 6/22/2000 -- New built in function, $notifywindows()
	Returns the windows that have been notified since they were last
	hidden.  Exactly the same as the %F status line expando.

*** News 6/22/2000 -- $chanwin() function now works for all channels
	It used to only support current channels, now you can get the window
	refnum of *any* channel.

*** News 6/22/2000 -- Support for /SET MAIL 3
	If you /SET MAIL 3, then epic will do everything it does in
	/SET MAIL 2, and it will also reset the mtime and atime for your
	mail box after it is done reading it.  This is neccesary if your
	mail reader gets confused if someone else reads your mailbox while
	it is running.

*** News 6/22/2000 -- Support for compiling with bounds checking gcc
	If your 'gcc' has the bounds checking extensions, then you can
	supply the '--with-bc' flag when you run configure to use it.

*** News 6/22/2000 -- Support for IRCNet's +I channel mode
	This is now supported.

*** News 6/22/2000 -- New status expandos, %{1}S, %{2}S
	The status expando %{1}S expands to ...
	The status expando %{2}S expands to ....

*** News 6/22/2000 -- Support for DalNet's +c channel mode
	This is now supported

*** News 6/22/2000 -- Default output of /on msg_group changed
	If you do not hook /on msg_group, then the default output format
	for the client will now look different than /on public_notice.

*** News 6/22/2000 -- Holy cow!  He finally updated this file!
	Yes, this file documents all of the userland changes since the
	last update, around December 1999.  Sorry for the delay

[Note -- this file only contains changes since the last release.
 For some releases, this means this file will be empty.  The entire
 file can be found at http://www.epicsol.org/UPDATES]

