dslinux/user/bitchx/doc BitchX.1 BitchX.bat.in BitchX.devel BitchX.doc BitchX.faq BitchX.mailinglist BitchX.sites BitchX.xpm Makefile Makefile.in README README.GTK README.OS2 botlink.txt entire-faq.html functions.txt hooks.txt ircII.servers mirc-colors.txt plugins.txt

stsp stsp at user.in-berlin.de
Sun Jul 2 15:18:38 CEST 2006


Update of /cvsroot/dslinux/dslinux/user/bitchx/doc
In directory antilope:/tmp/cvs-serv9280/doc

Added Files:
	BitchX.1 BitchX.bat.in BitchX.devel BitchX.doc BitchX.faq 
	BitchX.mailinglist BitchX.sites BitchX.xpm Makefile 
	Makefile.in README README.GTK README.OS2 botlink.txt 
	entire-faq.html functions.txt hooks.txt ircII.servers 
	mirc-colors.txt plugins.txt 
Log Message:
Adding pristine copy of BitchX so I can branch from it.


--- NEW FILE: functions.txt ---
BitchX function doc.  
Last updated: 9/10/98 by power <power at power.zepa.net>

This is not a complete function manual.  For all functions
please look in ../bitchx-docs/6_Functions/



Function: $left()
Usage:    $left(number text)
Returns:  the <number> leftmost characters in <text>.
Example:  $left(5 the quick brown frog) returns "the q"

Function: $getkey()
Usage:    $getkey(channel)
Returns:  the channel key if there is one.
Example:  $getkey(#BitchX) should return nothing ;)

Function: $right()
[...1067 lines suppressed...]
            <none> <none> <none> <none> "" "" <none> <none> NONE

Function: $chanmode(#chan num)
Usage:    $chanmode(#chan num) - 'num' can be one of 0=normal, 1=bans,
          2=ban whoset time, 3=exemptions for TS4.
Example:  /do echo $chanmode(#BitchX 1) returns "*!*@*.aol.com"
          /do echo $chanmode(#BitchX 2) returns "*!*@*.aol.com power 7812"

Function: $channicks(#chan sort_type)
Usage:    $channicks(#chan sort_type) - 'sort_type' can me one of:
          0=normal, 1=none, 2=nick, 3=host, 4=time, 5=ip (if available)
Example:  /eval echo $channicks(#BitchX) returns nicks on #BitchX
          /eval echo $channicks(#BitchX 3) returns nick on #BitchX
            sorted by host.

Function: $topic(#channel)
Usage:    $topic() or $topic(#channel)
Example:  /eval echo $topic() returns topic on current channel.
          /eval echo $topic(#BitchX) returns topic on #BitchX.


--- NEW FILE: entire-faq.html ---

<HTML>
<HTML>
<HEAD>
</HEAD>
<BODY BGCOLOR="#FFFFFF">
<TITLE>BitchX FAQ</TITLE>


<table border=0 cellpadding=0 cellspacing=0 width=100%>

	<tr>
	<td bgcolor='c7cde3'><b>Entire BitchX FAQ</b></td>
	</tr>

	<tr>
	<td bgcolor='dddddd'>
<b>[FAQ Section 1 :: <b>General Information]</b></b>
<br><br>
[...1555 lines suppressed...]
Workaround:<br />
<br />
Use Window-specific logging instead (/window logfile and /window log on), or install a logging script like bxlog.<br />
</code>
<br><br>
<i><b>fo shizzle</b></i><br>
<code>to fizzle_b</code>
<br><br>
</td>
</tr>
</table>
</CENTER>
<BR><BR><BR>

<font size='1'>
$Id: bitchx-faq version 5 by power
</font>

</BODY>
</HTML>

--- NEW FILE: BitchX.bat.in ---
@ECHO OFF

REM @configure_input@

REM This is your realname.
SET IRCNAME=BitchX for Windows User

REM This is a list of servers to connect to, separated by a ":". If the first
REM one can't be connected to, then the next one is used, and so on.
SET IRCSERVER=irc.primenet.com:irc.cs.cmu.edu:irc.mindspring.com

REM This is your username or ident.
SET IRCUSER=WinBitchX

REM This is your nickname.
SET IRCNICK=WinBitchX

REM This is your usermode.
SET IRCUMODE="+iw"

REM REM This is the vhost you want to use, if applicable.
REM SET IRCHOST="WinBitchX.com"

REM This is the name/path of the BitchX executable to run.
REM -c #BitchX (joins #BitchX on startup)
REM -l bx-rc (load bx-rc on startup)
@_VERSION_@@EXEEXT@ -c #BitchX -l bx-rc

--- NEW FILE: README.OS2 ---
The OS/2 portion of the BitchX client is no longer supported and will not
be maintained in BitchX2.  If you have troubles with this software you can
attempt to contact the former maintainer but be aware that he may no longer
have any interest in updating or fixing problems with the OS/2 portion of
the client.

sin at bitchx.org/EFnet@#BitchX

------


This is a port of the latest BitchX to OS/2 Presentation Manager. (3-25-02)

Several environment variables should be set before running PMBitchX.

As of this version you can let the installation program set these, 
or you can do it yourself.

HOME = your home directory, where you will place scripts and other things.

USER = your username

IRCNAME = PMBX User's name

IRCNICK = PMBXUser

HOSTNAME = mycomputer

Scripts are located at scripts.bitchx.com. To install untar them into the
HOME directory and /load them.  Also try /load menu.bx for pull down 
menus. If it is a clean installation and you don't have the HOME environment
variable set... it should load automatically.

What's new in 1.0c19:

Fixed multiserver issues resulting from script calls from the
GUI thread with from_server set incorrectly.

Updated to the latest version of Dynamic Windows.

Memory leaks and buffer under/overrun fixes, should be very
stable now.

Probably alot more but I've been distracted with other projects
and this code has been developing for over a year.

What's new in 1.0c17:

Lots of bug fixes to the main BitchX source.

Fixed another multiserver bug.  from_server was pointing
to the wrong server when the EVKEY message made it back to
the main thread.  This affected any GUI BitchX's.

What's new in 1.0c16 release 4:

Fixed saving of the MDI variable. (as well as a few others)

Fixed a bug in /window delete.

Added double click keybindings.

Updated script to use these keybindings to open query windows.

Added Saving of the nick at network time date in the "Comments"
Extended Attribute.  So you can tell when and where a file
came from.

Fixed some major multiserver issues.  Some issues still exist.

Updated to the latest version of dynamic windows.

Fixed a bug where the window size was set to 0 when a window was minimized.

Fixed size bug of the minimized icons in MDI mode.

Added virtual host support.

Fixed a couple timer bugs.

Fixed a crash when trying to detach shared menus from a menu that
didn't exist.

PM About box.

What's new in 1.0c16 release 3:

MDI fixes, resizing flips the y component.

Enhanced codepage support with tips from mikh.

Fixed a bug where BitchX was attempting to operate on dead screens.

What's new in 1.0c16 release 2:

Once again updated the installer.  Fixed a bug in release 1 installer
which caused crashes when updating CONFIG.SYS.

Fixed a bug which *VERY* intermittently caused crashes when updating
the cursor (blink).

Fixed crashing when loading the script (when comparing against a 
string with "infinity" in it... i.e. in the server list).

Removed MMPM dependency.  Now when starting up it tries to load
MCIAPI.DLL and if it fails it disables sound support.

Fixed a crash bug when SERVER_GROUPS is enabled, and it cycles 
through all the server entries.  

What's new in 1.0c16:

Updated script to allow CTRL-X to switch windows as well as channels.
If you turn off JOIN_NEW_WINDOW please also disable the rebinding of CTRL-X.

Added some keybindings to bx-rc to make things easier.
If you are an OpenChat user you may want to edit the bx-rc
and uncomment a couple lines.

Fixed crash bug when reloading menu.bx.

PMPaste now pastes to your query.

Fixed window close crash bug.

Fixed Switch List to show only one window in MDI mode.

Fixed background not redrawing in the MDI window in certain conditions.

Added attached nicklist.

Script enhancements to take advantage of the nicklist.

Preliminary MDI code ... it's buggy in spots.

New JOIN_NEW_WINDOW_TYPE, QUERY_NEW_WINDOW and QUERY_NEW_WINDOW_TYPE.
Allows the JOIN_NEW_WINDOW variable to be used in console clients.

Since DavidW2 and pana reautoconfed BitchX PMBitchX can now be configured
via the configure script with the following options:
./configure --with-pm --enable-sound

Rewrote the copy code.  It now allows you to select the entire window.
Fixed a bug where it was using the wrong character size during the 
selection when more than one font is in use. It now strips trailing 
white space from the end of the line.

Added tab stops to the properties notebook so it can be manuvered with
the keyboard.

New shared menu code in line with OpenChat.

New function $menucontrol().

Rewrote the font dialog, dialog is bigger, has the option to 
change the font for all windows. No longer blocks the UI while
the dialog is open.

Fixed a key binding problem with the delete key.

Script updated to demonstrate the new functionality. (settings menu)

New command /dialog in the source tree althought disabled for release
because it is to incomplete/buggy at the moment.

Debating best fix for keybinding differneces on OS/2 and Unix.

What's new in 75p3 (rel 3):

Fixed a bug in /window setwindowpos which core if the improper
number of arguments was used.

Fixed the scrollerbars in the pm and gtk, so they no longer use
the bug work around in clients prior to 75p3.

Fixed a bug which made /window menu -delete not function.

What's new in 75p3 (rel 2):

Bug fix for window #10 cores.

ajoin, invite etc now obey the JOIN_NEW_WINDOW parameter.

The Join menu now works properly.

/window setwindowpos implemented.

Bug fix in $winitem() so it properly returns the current position
in pmbx and gtkbx.

$screensize() implemented.

Various updates to menu.bx.

What's new 75p3:

Renamed bxmenu.bx to menu.bx (which is what is used in gtkbx).

Several menu.bx fixes, including adding the "quiet" alias.

Merged with the latest source, fixed a bug with event sending when more
than 10 windows were open.

Fixed a bug in the nicklist when the window in focus was not on a channel.

What's new 75p2 (rel3):

Fixed a bug where the maximum file descriptor limit was incorrectly set to
16, it is now set to FD_SETSIZE (which in emx 0.9d is 256).  Solves a 
core problem with a large number of DCCs.  

Fixed a plugin bug where it would loop infinitely when there were less than
20 nicks on a channel.

Fixed /window show to properly change the current focus.

What's new 75p2 (rel2):

Readded /exec code fixes, and file dialog code that didn't get merged. 

What's new 75p2 (rel1):

Fixed a bug in the input line.

Subsequent calls to /nl (nicklist plugin) now correctly turn the
nicklist on and off.

Updated the nicklist plugin so you can /set nl_always_on_top on.

Using new keybinding code.

Fix for Aurora/Trident/GRADD/Cirrus Logic drivers. (IBM misdocumentation)

Based on BitchX 75p2 (public) code, merged with main distribution.

I have created an XP-like interface in the source code to ease
porting to other OSes.  A preliminary gtk port is available.

Some performance changes in the caching code.

File dialog no longer blocks the window which it was called from.  
It now runs in a separate thread. 

Added a clist window scripting function.

Fixed a bug in $servergroup() which caused the script to screw up
in the server menu server list.

Fixed a bug in /window show which caused a crash when used with 
hidden windows.

Added SIGINT on CTRL-C to allow you to break out of a server connect.
(In both pmbx and gtkbx)

Changed the installer to not add IRCSERVER to the CONFIG.SYS.

Readded a couple patches that got missed in the last code merge.

Fixed the corruption bug in gui_clreol().

Known bugs:

No PM specific ones known at the moment.

Please don't report the above as bugs, I already know about them. :>

Please send any comments to dbsoft at technologist.com

--- NEW FILE: Makefile.in ---

SHELL = @SHELL@

default:
	$(SHELL) ./configure --with-plugins

--- NEW FILE: plugins.txt ---

			BitchX Plugins
			Written by Colten Edwards (c) 1997


Plugins can be created for BitchX quite easily. All plugins you create will
have a startup function which is based on the filename of the plugin and 
_Init appended to it. So for a module like cavlink.so we have a startup
function called Cavlink_Init(). Cavlink_Init is defined as the following

int Cavlink_Init(IrcCommandDll **interp)
{
}

returning a 0 indicates successful installation, any other return is an
error.

You can add various commands, variables, functions, tcl functions, and ctcp
to the main client itself. You have complete access to ALL variables defined
within BitchX itself. 

There is also a functions that may or may not be defined by you called the
fini function. Once again it's based on the filename appended with _Cleanup
to give us

int Cavlink_Cleanup(IrcCommandDll **interp)
{
}

If you make a cleanup function, you are responsible for removing all traces
of your dll from the client.

Adding a new command/function/var in a plugin is made easier with a function
that I wrote to add them to BitchX while keeping track of what's loaded.

add_module_proc(type, module name, command name, description, 
		id, flag, function1, function2);

type can be any of the following
	COMMAND_PROC	(internal /command)
	ALIAS_PROC	(internal function)
	CTCP_PROC	(ctcp procedure)
	VAR_PROC	(a /set variable)
	HOOK_PROC	(like a /on hook)
	RAW_PROC	(lowlevel access to server output)
	DCC_PROC	(new /dcc commands)
	WINDOW_PROC	(new /window commands)
	OUTPUT_PROC	(replacement output procedure)

module name is for internal bookkeeping practices. It's displayed when we
list the loaded plugins, and is also used for finding what to remove in the
event of a /unloaddll. 

command name is the name of the procedure we are adding to the client. or
How we will call the procedure.

description is just a description for display in a usage() function. It can
be NULL as well.

id is used in a VAR_PROC HOOK_PROC and CTCP_PROC to identify some aspect of
the procedure. each "type" uses id differantly. A VAR_PROC uses this to
identify the type of variable being introduced ie. STR_TYPE_VAR,
INT_TYPE_VAR, BOOL_TYPE_VAR. A CTCP_PROC can be set to -1. HOOK_PROC uses
this to identify the hook to add this to. A negative number means this is a
server numberic to add too. A non-negative value is used to indicate a
particular hook. You can use the enumerated list of hooks in hook.h to make
this easier ie. CHANNEL_SYNCH_LIST.

flag is used in the same procedures as id. a VAR_PROC uses this as the
default INT/BOOL value for the variable. CTCP_PROC uses this to tell the
client what todo when we recieve one of these ctcp's. CTCP_SPECIAL,
CTCP_TELLUSER, CTCP_REPLY, CTCP_INLINE, CTCP_NOLIMIT are possible values. 
These can be or'd together as well. HOOK_PROC uses this as the "noise"
of this event.

function1 is the function to call for this particular command. This always
needs to be supplied for all the various procedures.. Even a VAR_PROC can
have a function associated with it.

function2 is the reply function for CTCP_PROC. It can be NULL.

Depending on the nature of the procedure your adding, determines what the
return from that procedure should be. a $function should return a string for
example. a command or a var procedure returns nothing. 

void command_proc(IrcCommandDll *, char *, char *, char *, char *);

void var_proc(Window *, char *, int);

char *alias_proc(char *);

char *ctcp_proc(CtcpEntryDll *, char *, char *, char *);

void hook_proc(int hook, char *buffer, char *);
void hook_proc(char *name, char *buffer, char *);

int raw_proc(char *num, char *from, char *userhost, char **Args);

void dcc_func(char *name, char *args);

Window *window_proc(Window *, char **args, char *help);

void output_proc(Window *, const unsigned char *str);


Tcl commands can be added from a module quite easily. Just make sure that
that you call Tcl_DeleteCommand() when unloading the module. This means you
need to use a Cleanup function.

A output procedure can be defined. It replaces ALL output procedures for ALL
screens and windows. You will need to handle everything that the current
add_to_window() function in screen.c does by yourself. You can however use
any or all of the BitchX functions. When removing this procedure, ALL
screens and windows are reset back to the default output procedure.


--- NEW FILE: Makefile ---

SHELL = /usr/local/bin/bash

default:
	$(SHELL) ./configure --with-plugins

--- NEW FILE: README.GTK ---
GTKBitchX is no longer supported.  It is bloated and eats a lot of CPU.

If you have problems with the GTK client do not ask us for help.  The GTK
client has not been updated or supported and we will no longer support it
in BitchX2


Minimum requirements for gtkBitchX:

GTK and GLIB 1.2.0
<http://www.gtk.org/>
 
imlib 1.9.4
<http://www.labs.redhat.com/imlib/>
 
pthreads
 
zvt from gnome-libs 1.0 (1.2 fixes the scrolling bug)
<http://www.gnome.org/>
 
esound (ESD) 0.2.5 and audiofile 0.1.5 for sound support
<http://www.tux.org/~ricdude/EsounD.html>
<http://www.68k.org/~michael/audiofile/>
 
Building GTK:
 
./configure --with-gtk
 
For ESD sound support:
./configure --with-gtk --enable-sound

Known bugs:

Paste doesn't work in MDI mode.
When the menu is added during window creation it screws up the size of 
	the window.  I need to find a way to delay adding of the menu
	until the window size has been solidified.

Changes:

Closed stdin/stdout/stderr to prevent problems with the 
	starting terminal on gtkBitchX exit.
Fixed background operation on Linux (and possibly others).
	SIGTTOU would be called repeatedly on Linux, on
	FreeBSD using nothing() would stop it's occurance.
	It now uses SIG_IGN instead of nothing().
Fixed a sizing bug with the nicklist enabled.
Added tab highlighting in MDI mode thanks to DavidW2.
Added a graphical about box and window icons courtesy of DavidW2.
Added MDI code using the GTK notebook widget.  This is not quite
	what I had originally envisioned but it will work for the
	time being.
Determined that the size bug is caused by creating the menu at
	the same time as the window.  The window is too small by the
	height of the menu.  Workaround in the works.
Fixed a bug with ESD not finding the sound files.
Code merged back into the main source.
Added ESD sound support to allow $mciapi(playfile filename) to function
	as it does in PMBitchX.
Fixed a bug where the font sizes were not saved when gtkbx falls back
	to the default fonts.  Pointed out by sideshow and MNC.
Fixed the window #1 corruption problem.  It turned out to be in my
	failsafe code which was to make sure there was a screen to send
	the text to.
Reimplemented shared menu code.  It now works as designed however when
	changing a shared menu it recreates the menus which results in
	excessive drawing.  I am looking for a way to prevent the
	redrawing (or at least reduce it).  Also looking for a way to
	improve the look of the checks... currently "X".
Added shared menu code from the PM version and then removed it because
	GTK does not allow internal sharing of widgets.  I guess I'll have
	to code a database of menus and widgets which are theoretically
	the same. (that won't work either because once it's attached it
	can't be changed).
Bits are now used to store menu types to facilitate having more than
	one type for a menu item.
Merged with the new BitchX 1.0 beta source.
Rewrote the tputs code so it's definition won't conflict on some systems.
Fixed a bug which was coring on first window creation in very rare 
	conditions.
Readded the flash code to attempt to solve a weird charset problem.
Reentrancy is impossible until gtk becomes thread safe so I added two, 
	functions gui_mutex_lock() and gui_mutex_unlock() to allow 
	plugins to call gtk functions safely.
Removed SIGUSR1 signal trapping on glibc 2.0 systems, because SIGUSR1
	and SIGUSR2 are used by threads.  
Removed bxzvt.h and added a fix for the zvtterm.h header.  Zed (zvt 
	author) will be adding this fix to the current codebase but
	the fix is still required for previous installations.
Changes to configure to allow clean compiling on *BSD, and remove 
	temporary files.
Zed also has proportional fonts working, so proportional fonts will
	be supported by gtkBitchX if using a version of zvt which 
	supports proportional fonts. I'll note which versions do when
	they are available.
Implemented /exec -start for unix.
Implemented /window font <fontname> to allow the font to be set via 
	a script, and to maintain OpenChat compatibility.
Tried to fix the window clear bug... mostly got it working... seems to
	clear the first line of window #1.

If you notice any other bugs, or have any questions email me at
dbsoft at technologist.com or visit #BitchX on EFNet.

Thanks!

Brian Smith

--- NEW FILE: hooks.txt ---
This is some information provided for script writers about the extra hooks
that BitchX provides for you. You can either use these or not depending on
what you like to see. This list is being added to and I will try and keep
this file updated for them. Thanks to "suicide" for pushing me into this :)
suicide writes the Whirred script for BitchX

MSGLOG  returns  
	timestr 
	type 
	from 
	what they sent.
	-or-
	timestr
	"On"
	fully expanded filename
	-or-
	timestr
	"Off"

BANS returns 
	the number we consider this to be
	channel
	the ban itself
	who set it.
BANS_HEADER

CDCC_PREPACK
CDCC_POSTPACK
	type   NOTICE or PRIVMSG
	from
	nickname
	active dcc's
	send limit
	number in the queue
	queue limit
	max dcc rate out
	number of bytes sent in this session.
	max dcc rate in
	number of bytes received in this session.
	total size of the packs we're offering
	minimum dcc speed we require.

CDCC_PACK
	type    NOTICE or PRIVMSG
	channel
	num of this pack
	number of files in this pack
	size of this pack
	number of gets for this pack
	the description.

CDCC_NOTE
	type   NOTICE or PRIVMSG
	channel
	note for this package

CDCC_QUEUE
	nick
	time
	pack num
	number of files
	description

BOT_LIST
	Auto op
	protected
	nick
	channels comma separated.
	host
BOTLIST_HEADER

CHANNEL_SYNCH
	channel
	time to join

KICK_LIST
	who
	from
	channel
	comment
DCC_HEADER      /* display before DCC_STAT* */
	"Dccnum"
	"type"
	"num"
	"status"
	"K/s"
	"File"
	"Encrypt"
DCC_POST        /* display after DCC_STAT*  */
	"Dccnum"
	"type"
	"num"
	"status"
	"K/s"
	"File"
	"Encrypt"

DCC_STAT
	/* this hook displays only dcc like chat's raw etc */
	number
	type
	user
	status
	"N/A"
	Description
	"E" for encrypted or nothing.

DCC_STATF
	/* this hook should only display files being transfered */
	Same as above.
	except kilobytes instead of "N/A"

DCC_STATF1
	percentage of file transfer'd
	bytes transferred.
	filesize
	minutes
	seconds

DCC_TRANSFER_STAT
	/* for /dcc stats command */
	bytes in
	max rate in
	min rate in
	bytes out
	max rate out
	min rate out
	number of dcc's
	active dcc's
	send limit
	Dcc Auto get "On" or "Off"
	show dcc paths "On" or "Off"
	Dcc quiet mode "On" or "Off"
	Dcc overwrite mode "On" or "Off"

JOIN_ME
	channel we just joined.
	/* useful for setting individual channel cset's */
LLOOK_JOIN
	name of server
	name of server link
	hopcount

LLOOK_ADDED
	name of server
	name of server link
	hopcount

LLOOK_SPLIT
	name of server
	name of server link
	hopcount

STAT_HEADER
	Nick
	Dop
	kicks
	nicks
	publics

STAT
	nick
	dop count
	kick count
	nick change count
	public count

USERS_HEADER
	Level
	Auto op
	protection
	Channel
	Nick
	+o
	UserHost

USERS
	Users level in our userlist
	Auto op ?
	Protect ?
	Channel/Channels comma separated.
	nickname
	Hostname
	chanop ? '@' :''

USERLIST
	Level
	Aop
	Prot
	nick
	host
	channel(s) comma separated.
	Password
USERLIST_HEADER

NOTIFY_SIGNOFF_UH
	Nick
	username
	hostname

NOTIFY_SIGNON_UH
	Nick
	Username
	Hostname

SAVEFILE
	Userlist and count
	-or-
	ShitList and count
	-or-
	AutoJoin and count
	-or-
	BotList and count
	-or-
	Notify and count
	-or-
	Idle and count
	-or-
	BanWord and count
		
SAVEFILEPOST
SAVEFILEPRE
	name of file we are saving to
	expanded name of file.

SERVER_NOTICE_FAKES
SERVER_NOTICE_FAKES_MYCHANNEL
SERVER_NOTICE_FOREIGN_KILL
SERVER_NOTICE_KILL
SERVER_NOTICE_LOCAL_KILL
SERVER_NOTICE_SERVER_KILL
	for nickname
	from who
	reason
	server
	other
	/* note some of these depend on /set's being on in order to provide
	   the information. SHOW_UNAUTH's SHOW_FAKES, SHOW_SERVER_KILLS,
	   SHOW_SERVER_CRAP in particular.
	 */

SERVER_NOTICE
	depends on /set SHOW_SERVER_CRAP on/off
	from nick
	line to display

SHITLIST
	level of shit to apply
	uh filter 
	channel(s) comma separated
	reason for shitlist
SHITLIST_HEADER

SHOWIDLE_HEADER
	channel
	idle time allowed

SHOWIDLE
	nick
	host
	userlevel in the userlist
	idle time

CHANNEL_STATS (32 parameters)
	channel
	complete date time in Mon Jun 10 01:20:03 1996 format. channelcreation
	time on channel in 0d  0h  0m 20s format
	mem usage total size
	mem used by nicklist
	mem used by channellist itself
	mem used by banlist
	stats_ops
	stats_dops
	stats_bans
	stats_unbans
	stats_ops
	stats_dops
	stats_bans
	stats_unbans
	stats_signoffs
	stats_joins
	totalbans
	maxbans
	stats_sops
	stats_sdops
	stats_sbans
	stats_sunbans
	usershere
	usersaway
	chanops
	chanunop
	totalnicks
	maxnicks
	numircops
	ircops 		list of nicks that varies.

USAGE   /* note still experimenting with this particular hook which may 
	   change at any time */
	command
	usage of command

DESYNC_MESSAGE
	channel
	server

HELPSUBJECT /* output from /chelp */
	name
	output

HELPTOPIC /* output from /chelp */
	name

WHOLEFT /* this list is expired after 20 minutes for those on the userlist
		and 10 minutes on the regular list. */
	nick
	userhost
	channel
	seconds since split
	their server
	my server
WHOLEFT_HEADER

USERS_SERVER
	nick
	server
USERS_SERVER_HEADER

AR_REPLY /* when the user presses ^] this hook is called with auto_reply
            nick to use passed to it. */
	nick 

CLONE_READ
	/* When information is ready on a socket this hook is called once
	   until $readsocket() is used.
        */
        socket number
        server name
        port

--- NEW FILE: BitchX.1 ---
.TH BitchX 1 "March 22, 2001" "" ""
.SH NAME
BitchX \- The Ultimate IRC Client
.SH SYPNOSIS
.B BitchX
[-aAbBcdfFHilLnNpPqrvxZ]
.SH DESCRIPTION
.B BitchX
is a VERY heavily modified ircII client.  It includes many things such as
built in CDCC (XDCC) offering, built in flood protection, etc.  It is easier
to script things in
.B BitchX
because unlike plain, vanilla ircII, half the script does not have to be
devoted to changing the appearance of ircII.  It also includes many other
new features, such as port scanning, advanced TCL, a CD player, a mail
client, screening process, etc.

.B BitchX - Based on
.B EPIC
Software Labs
.B epic ircII (1998).
Version (BitchX-1.0c18) -- Date (20010108).

.SH OPTIONS
.TP
.I -a
Adds default servers and command line servers to server list.
.TP
.I -A
Do not display the startup ansi.
.TP
.I -b
Load .bitchxrc or .ircrc after connecting to a server.
.TP
.I -B
Force 
.B BitchX
to fork and return you to a shell. pid check on.
.TP
.I -c <channel>
Joins <channel> on startup.
.TP
.I -d
Runs
.B BitchX
in "dumb" terminal mode.
.TP
.I -f
Your terminal uses flow controls (^S/^Q), so
.B BitchX
shouldn't.
.TP
.I -F
Your terminal doesn't use flow control (default).
.TP
.I -H <hostname>
Uses the virtual hostname if possible.
.TP
.I -i
Ignores your autojoin entries.
.TP
.I -l <file>
Loads <file> in place of your .ircrc.
.TP
.I -L <file>
Loads <file> in place of your .ircrc and expands $expandos
.TP
.I -n <nickname>
Nickname to use
.TP
.I -N
Do not auto-connect to the next server.
.TP
.I -p <port>
Default server connection port (usually 6667).
.TP
.I -P
Toggle check pid.nickname for running program.
.TP
.I -q
Does not load .ircrc or .bitchxrc.
.TP
.I -r <file>
Load <file> as list of servers.
.TP
.I -v
Tells you about the clients version.
.TP
.I -x
Run
.B BitchX
in "debug" mode.
.TP
.I -Z
Use NAT address when doing dcc.

.SH ENVIRONMENT
.TP
.BR BitchX
uses many environment variables to configure the client.  These can be set
by editing your ~/.profile or ~/.bash_login (if you're using a /bin/bash
shell) and adding ``export VARNAME="var value"''.  Or, if you are using the
tcsh shell you can set these by editing ~/.tcshrc and adding 
``setenv VARNAME "var value"''.  Below is a list of variables.
.PP
.TP
.BR IRCNICK
sets the default IRC nickname. eg, export IRCNICK="mynick"
.TP
.BR USER
sets the default username to use.  If not set, it uses a default value of
"unknown" - This will only work under NON-UNIX operating systems.
.TP
.BR IRCUSER
same as
.BR USER
.TP
.BR IRCHOST
sets the virtual hostname to use.
.TP
.BR IRC_HOST
same as
.BR IRCHOST
.TP
.BR IRCNAME
sets the name that appears in the "realname" field on your /whois.  The
default value is "* I'm to lame to read BitchX.doc *".
.TP
.BR IRCSERVER
sets the default IRC server to use.
.TP
.BR IRCPORT
sets the default IRC port to use.  Usually 6667.
.TP
.BR IRCPATH
sets the path from which files are loaded.  Default is ~/.BitchX/
.TP
.BR IRCUMODE
sets your default usermode.  Default is "+iw"
.TP
.BR IRCRC
sets the filename to be used in place of ~/.bitchxrc or ~/.ircrc
.TP
.BR IRCLIB
sets the 
.B BitchX 
library path (Used for some small example scripts).
.TP
.BR IRC_SERVERS_FILE
sets the name of the IRC server list that is loaded before any other lists.
.TP
.BR IRCFINGER
sets your CTCP FINGER information.
.PP
.SH FILES
.TP
.I ~/.bitchxrc
Loaded by
.B BitchX
when it is started.
.TP
.I ~/.ircrc
If 
.BR ~/.bitchxrc 
is not there, this file is loaded on startup instead.
.TP
.I ~/.ircservers
Contains a list of IRC servers to cycle through.
.TP
.I /usr/local/lib/bx/
System-wide configuration dir.
.TP
.I ~/.BitchX/BitchX.sav
Personal configuration file.
.TP
.I ~/.BitchX/BitchX.ircnames
Default random real name.  NOTE: Must be copied from /usr/local/lib/bx/
.TP
.I ~/.BitchX/BitchX.formats
Personal 
.B BitchX 
display formats.
.TP
.I ~/.BitchX/BitchX.reasons
Default random kick messages.  NOTE: Must be copied from /usr/local/lib/bx/
.TP
.I ~/.BitchX/BitchX.quit
Default random quit messages.  NOTE: Must be copied from /usr/local/lib/bx/
.TP
.I /usr/local/lib/bx/BitchX.help
.B BitchX 
help file.
.TP
.I ~/.BitchX/screens
Screen storage for a detached
.BR BitchX
session.
.PP

.SH OBTAINING
You can always download the newest version of
.B BitchX
by joining #BitchX on EFNet and typing "/offers" in the channel window.  To
check what the latest version is type "!explain latest" and the bot will
tell you.  You can also ftp to 
.B ftp.BitchX.com 
to get the latest client, scripts, tcl objects, documentation, and many other
useful items.  You can also point your browser to 
.B http://www.BitchX.com
for some more things.
.PP
.SH BUGS
Please report all bugs to an op on #BitchX on EFNet, e-mail panasync or send
an e-mail to the mailing list.

.SH MAILING LIST
There is a BitchX mailing list, to subscribe simply send an e-mail to:
.B majordomo at lists.BitchX.com 
with only the words "subscribe BitchX" in the body.  You will receive
another mail to confirm this and once you have replied you can post to the
list by sending e-mail to
.B bitchx at lists.BitchX.com.
This is a helpful place for bug reports

.SH MAN PAGE ORIGINAL AUTHOR
Wichert Akkerman
.B <wakkerma at debian.org>

.SH MAINTAINER
Robert Durdle - Dragoon at EFNet
.B <robert at durdle.com>

dialtone
.B <dialtone at chemlab.org>

.SH BitchX Author
Colten Edwards
.B <edwards at bitchx.dimension6.com>
.PP
panasync

.SH Responsible for ports to other OS's
Brian Smith
.B <dbsoft at technologist.com>
.PP
nuke


--- NEW FILE: BitchX.doc ---
You might find useful information in this file, even though it is outdated.

Please visit http://faq.bitchx.org/ for current FAQ and Documentation.


		
		Welcome to the documentation for BitchX for 
 		Windows 95/98/2000/NT/UNIX/OS/2/MacOS

BitchX is written and supported by me Colten Edwards (aka panasync at efnet).
BitchX represents a quite alot of my free time in the last 4 years.
I only hope that you enjoy using the client. It was written because of the
lack of what I considered a nice client under unix. Nice meaning a client
that included source and had features that were typically scripted adding to
the memory usage and cpu usage of the defacto client of the time ircii-2.8.
I had looked at epic 3, but considered it flawed at the time I looked at it.
After muddling around the ircii-2.8 source for several months I was able to
come up with something that added a few new features and thus BitchX was
born. At first BitchX was passed from person to person on irc as source
[...1176 lines suppressed...]

If you really like the program and wish to help the author.
	Box 275
	Conquest,SK
	S0L-0C0
	Canada

Hardware, donations, postcard, even job offers :)


                            Favorite IRC Client
                      Displaying results of the poll.
               BitchX   [INLINE] [INLINE] [INLINE] 1386 / 36%
                 Kirc   [INLINE] [INLINE] [INLINE] 148 / 3%
                ircII   [INLINE] [INLINE] [INLINE] 713 / 18%
                Mirc   [INLINE] [INLINE] [INLINE] 419 / 10%
                 Virc   [INLINE] [INLINE] [INLINE] 180 / 4%
                 Epic   [INLINE] [INLINE] [INLINE] 235 / 6%
                Other   [INLINE] [INLINE] [INLINE] 507 / 13%
                             3818 total votes.

--- NEW FILE: mirc-colors.txt ---
About Control-C colors

If your client was compiled with #define CONTROL_C_COLORS and you have
/SET CONTROL_C_COLORS ON, then you can use the control-c colors feature.
The general syntax is:

color-seq-start := "^C" [number] ["," number]
color-seq-end   := "^C"

The first "number" is a positive integer at least 0 and not more than 15.
The colors correspond to the ANSI color schema:

	0 - black 	1 - red		2 - green	3 - yellow
	4 - blue	5 - magenta	6 - cyan	7 - white

The colors 8 through 15 are the corresponding "bold" versions of the colors
above, whatever that may be for your terminal.

The "standard" as imposed by mIRC forbids an empty leading value.  This
implementation imposes this draconian restriction.  In fact, it is treated
as an end-of-color delimiter.  So there.

If you wish to defeat the color codes, you can have them filtered out by
doing /SET CONTROL_C_COLORS OFF.


OUR REVISIONS TO THE "STANDARD":

The syntax of colors has been modified to:

color-seq-start := "\003" + color-term + ["," color-term]
color-term      := ["0" + ["0..9"] | "1" + ["0..5"] ] | ["2..9"] | [""]
color-seq-end   := "\003"

Specifically, this implementation guarantees that at least zero and at most
two character will ever be used to construct the color code.  If the first
character is a 0, then the second character will be used if it is a number.
If the first character is a 1, then the second character will be used only if
it is a number at least 0 and at most 5.  A comma following the first color
term will only be "eaten" if it is followed by another valid term.

Either the first term or the second term may be empty.  If either term (but
not both) are ommitted, then no change will occur for that modifier.  If both
terms are omitted, the comma must also be omitted, and all color attributes 
will be terminated.

It is hoped that this clarification will allow the deterministic use of color
codes (if you always use two digit codes, then you will never have a problem
with the color codes munching too many characters.)

-end of file-

--- NEW FILE: botlink.txt ---
BitchX bots mini-howto.. by Rwf, date: 08/17/97

Table of contents:
	(1) Overview of BitchX's bot mode
	(2) Basic steps to link two (or more) clients
	(3) Using the partyline
	(4) Frequently asked questions
	(5) Contacts / miscellaneous information

Note: this document targets BitchX 72p2 and higher.. if you don't have
	at least 72p2, check out the contacts section info on how to get
	a newer copy of BitchX.


(1) Overview of BitchX's bot mode

BitchX includes an eggdrop-like bot mode.. it allows you to create a DCC
'partyline' between several BitchX clients. This document explains how
to create a network like this, and answers some of the questions surrounding
the linking in general.

(1a) Single-bot partylines

Yes, it is possible to create a partyline on just one client. It looks a
little like this:
			Bot A
	   Client A  /    |    \ Client C
		          |
		       Client B  

In this situation, Clients A, B, and C can be any kind of IRC client who
is active in a chat with Bot A. Bot A relays all the text between the three
clients, allowing them to talk to each other through the bot. 

(1b) Dual-bot partylines

Dual-bot partylines are structured like this:

		Bot A  -------------------------------	Bot B
     Client A /	  |			     Client C /  |    \ Client E
		Client B			       Client D

Here, Bots A and B are linked together. Clients A and B hold DCC chat 
connections to Bot A, while clients C, D, and E have DCC chat connections
to Bot B. On each of the bots, the chat works the same way as it does in
the single-bot situation. However, the two bots also relay the information
between themselves, and pass that information on to their clients. For
example, if Client A typed a line of text, that same line would show up
on Client C's screen as Client A's nickname followed by Bot A's nickname,
to let Client C know where the message was coming from.

(1c) Three (and more) bot partylines

		     Client A \       / Client B
				Bot A
			Bot B /	      \ Bot C -- Client F
	     Client C /   |		  |
			Client D	Client E

In this diagram, Bot A serves as the hub bot. Bots B and C are linked to
Bot A, and all the bots have clients attached to them. Here, if Client A
sends a message, it is relayed to Bots B and C by Bot A, as well as being 
relayed to Client B. Bots B and C take the message and further relay it to
their clients. Now, if Client F were to send a message, the message would
be relayed by Bot C to Bot A and Client E. Bot A would pass the message to
its clients, and to Bot B, which would further pass the message along to
the clients attached to Bot B.

More complicated uplinks are possible, but i'm getting a little sick of
drawing nice pictures. :)  Section 2 explains how the linking takes place.


(2) Basic steps to link two (or more) clients

This can be done in just a few steps, but you have to pay attention..
Notice: This is not for the idle-minded, stop by #teenchat sometime. :)

a) Make sure you actually have two (or more) clients to do the linking
    with. How you choose to run the clients is up to you, although a lot
    of people (including myself) prefer running them under screen. again,
    check the contacts section to find out how to get screen.

b) Decide which bot you want to be the hub bot.. it doesn't make too much
    difference in a two-bot network, but its always nice to have a 
    designated driver, you know? :)

c) Pick a bot to start with.. (preferably the hub, unless you enjoy doing
    things the hard way like a complete fool)  Use the /addbot  command to
    add each of the other bots to the internal bot list. The syntax of the 
    /addbot command is this:

	/addbot BotB #MyChannel 2 2 i_am_lame
	   |      |       |     | |    |
   the command    |       |     | |   password 
		bot nick  |     |  \
                         /      |    protection level
		channel for bot  \
				   auto-op level
   notes:
    BotB - the nickname can also be a hostmask.. however, you MUST specify
	    a nickname somewhere. for example, BotB!*mybot@*.lame.net
    #MyChannel - channel the bot will sit in
    auto-op - desired auto-op level for the other bot, just like in a
		normal userlist. see /bhelp userlevels
    protection - always a good idea to wear it.
		   oh come on, that should be self-explanatory.. :)
    password - this is a *MUST-HAVE* !!!! its a good idea to make sure
		its the same thing across all the bots... either that
		or i hope you own stock in Tylenol.

   For each of the non-hub bots, use the same procedure to add the hub
    bot to the botlist. Its pretty simplistic.

d) Now that all the bots know who each other are, its time for a formal
    introduction. (if you have more than two bots, start with the hub and
    one of the other bots, add the rest later.)  From the hub bot, issue
    this command:

	/dcc bot BotB

    where BotB is the nickname of the second bot. This will send the second
    bot a DCC BOT request, which will be checked against its bot list.

   Next, flip over to BotB, and enter the command:

	/dcc bot BotA

   You should already have seen some CTCP & DCC messages from BotA, and
    issuing that command causes BotB to finish off the link.

   To test the link, type this:

	/csay hi there

   This will send a message as if the bot itself was speaking. Try looking
    at BotA to make sure the message showed up.. it should look like this:

	(BotB(xlink)) hi there

   If you see a message like that, you're in business. Read on.

e) Finishing touches.. 

	1. make sure every bot has its settings correct..
	    type /set bot  , and check these settings:

.......................BOT_LOG ON
...................BOT_LOGFILE tcl.log
......................BOT_MODE ON
....................BOT_PASSWD has no value
....................BOT_RETURN has no value
.......................BOT_TCL OFF

	The most important setting being BOT_MODE .. make sure its 
	 turned on, otherwise the bot will refuse DCC chats.
	
	2. In BitchX 72p2 and up, the bots will only accept chats from
	    persons in their userlist (see /bhelp adduser  for details),
	    *OR* persons who have been .invite 'd into the chat session.
	    See the command list in the next section for details.

	3. Make sure to do a /saveall to save all important settings.


(3) Using the partyline

To join the partyline, start a dcc chat with one of the bots. After the
DCC is connected, type .chat   into the DCC to join the partyline. You
can then talk to any other people already there, and use the available
commands in the DCC:

	.act <action>           - sends <action> to chat line
	.boot <nick> <msg>      - boot <nick> from network
	.chat                   - once a dcc is started send .chat to enter
	                          the party line
	.cmsg <nick> <msg>      - sends <msg> to <nick> in chat
	.echo                   - toggle echo back to you on/off
	.help <topic>           - help for commands or <topic>
	.invite <nick>          - invites <nick> to join the partyline
	.msg <nick> <msg>       - send <msg> to <nick>
	.say <msg>              - say <msg> to the channel
	.quit                   - quit partyline, but not the chat.
	.tcl <tcl_command>      - tcl command
	.who <botnick>          - who is on bot or <botnick>
	.whom                   - shows all users on network

Just typing text in the DCC causes the bot to relay it to the partyline.

(4) Frequently Asked Questions

Its time for the big FAQ list.. a lot of these I asked myself at one time,
but its good info so be sure to read it ALL.

q) What's BitchX?
a) Uhm... this isn't the file you were looking for.

q) The bots didn't link but I have botlist entries for them each!
a) Check the passwords. They *MUST* be identical. Also check the usermasks
	for the bots for typos, etc.

q) The bots linked, but I can't chat to them.
a1) Make sure you've added yourself to the bot's userlists. 
a2) Make sure BOT_MODE is turned ON.

q) Some of the commands in the chat don't work.
a) Many of the commands require the specified userlevel in .help  to use
	them. Make sure to add yourself to the bot's userlist.

q) Can the bots share userfiles like in eggdrop?
a) No. The bots do not share userfiles..

q) Can the bots link to eggdrops?
a) No. Eggdrops link via telnet, not DCC.

q) Where can i get BitchX?
a) See the contacts section.

q) Where can i get screen?
a) See the contacts section.

q) Where can i get Windows?
a) Press the power button.

q) Can the bots share userfiles like in eggdrop?
a) Dumbass.

q) Who the hell is Rwf?
a) God.

q) Who the hell is panasync?
a) The big god.

q) Can the bots share userfiles like in eggdrop?
a) You can go away now.

q) Does chicken come in a can?

....

(5) Contacts & information

Where to get bX:

As always, there's the #BitchX channel on EFNet.
Get BitchX via FTP: ftp://aurora.bridges.edu
Get screen from the same places.

Contacts:

Rwf - find me on EFNet.. #Lb, or #BitchX. rwf at loonybin.dyn.ml.org
panasync - find him on EFNet too, in #BitchX.

--- NEW FILE: README ---
Last Updated: Tue Apr  8 16:16:03 EDT 2003

This directory contains documentation about BitchX and its features.

Documentation for an IRC Client like BitchX is never complete, if you
have any files you would like included here, please send them to powuh
in #BitchX on EFnet.



--- NEW FILE: BitchX.devel ---
    .sssSS$$s.s$$$$$$ $$sss..   s$$$^`$ss.   $$$$$s s$$$$  .s$$$$$s   s$s
 .$$$$$'  `$$$ $$$$$$ $$$$$$$$$s $$'   `$$$$s $$$'   `$$$  $$$$$$$'  s$$'
s$$$$'      `$s $$$$ $$' $$$ $$$ $      d$$$$s $$     $$$   `$$$$'  s$$'
$$$$$sss..ssS$'s$$$'s$' .$$' `$$ $     d$$$$$'s$$sssss$$$ $$$s`$$  s$'
$$$$$$$^^^^$$s $$$$     $$$  s  s$           s$$$     $$$ $$$$s`$$s' by 
$$$$'       `$$s $$     $$$s $$$$$       ..sSb $$     $$$      s$`$s panasync
$$$'         $$$s $    .$$$$ `$$$$     d$$$$$$ $$$    $$$    .$'  `$s.
$$$s.      .s$$$$ $$  .$$$$$  `$$$$s.   $$$$$$ $$$s   $$$   s$     `$$$$s
`$$$$Xavier$$$$$'s$$s $$$$$$s   `S$$sss$$$$$'s$$$$$  s$$$ s$$s      `$$$'

Last Updated: Tue Apr  8 16:00:01 EDT 2003

BitchX is looking for coders to help maintain the client, add new features,
and fix any existing bugs.  If you would be interested in helping, join #BitchX
on EFnet and let us know!

The BitchX Development Mailing List is available at bitchx-devel-request at lists.bitchx.org
Note, this is a closed mailing list and you will not be able to subscribe or post unless
you are approved for submissions.  In general, only people that will be approved for
submission are listed below.


If your name is not listed below, and you think it should be, contact powuh
in #BitchX on EFnet.  Anyone who actively finds bugs in BitchX, or who tests
new releases of BitchX is considered 'Quality Control'

Current BitchX Team:
	panasync	Original Author
	nuke		Lead code maintainer
	caf		Lead code maintainer

	sin		FTP Site Maintainer, Quality Control
	powuh		Documentaion/FAQ Maintainer, Quality Control
	Raistlin	Mailing List Maintainer

	sideshow	bitchx.org domain name owner
	MHacker		bitchx.com domain name owner

	BlackJac	Quality Control
	|Rain|		Quality Control
	void		Quality Control


--- NEW FILE: BitchX.mailinglist ---
    .sssSS$$s.s$$$$$$ $$sss..   s$$$^`$ss.   $$$$$s s$$$$  .s$$$$$s   s$s
 .$$$$$'  `$$$ $$$$$$ $$$$$$$$$s $$'   `$$$$s $$$'   `$$$  $$$$$$$'  s$$'
s$$$$'      `$s $$$$ $$' $$$ $$$ $      d$$$$s $$     $$$   `$$$$'  s$$'
$$$$$sss..ssS$'s$$$'s$' .$$' `$$ $     d$$$$$'s$$sssss$$$ $$$s`$$  s$'
$$$$$$$^^^^$$s $$$$     $$$  s  s$           s$$$     $$$ $$$$s`$$s' by 
$$$$'       `$$s $$     $$$s $$$$$       ..sSb $$     $$$      s$`$s panasync
$$$'         $$$s $    .$$$$ `$$$$     d$$$$$$ $$$    $$$    .$'  `$s.
$$$s.      .s$$$$ $$  .$$$$$  `$$$$s.   $$$$$$ $$$s   $$$   s$     `$$$$s
`$$$$Xavier$$$$$'s$$s $$$$$$s   `S$$sss$$$$$'s$$$$$  s$$$ s$$s      `$$$'


The Offical BitchX Mailing List

To subscribe to the BitchX User's List, send an email to:
	bitchx-users-request at lists.bitchx.org
with the word SUBSCRIBE in the body of the message.


This list is for general discussion about BitchX.

--- NEW FILE: BitchX.faq ---
    .sssSS$$s.s$$$$$$ $$sss..   s$$$^`$ss.   $$$$$s s$$$$  .s$$$$$s   s$s
 .$$$$$'  `$$$ $$$$$$ $$$$$$$$$s $$'   `$$$$s $$$'   `$$$  $$$$$$$'  s$$'
s$$$$'      `$s $$$$ $$' $$$ $$$ $      d$$$$s $$     $$$   `$$$$'  s$$'
$$$$$sss..ssS$'s$$$'s$' .$$' `$$ $     d$$$$$'s$$sssss$$$ $$$s`$$  s$'
$$$$$$$^^^^$$s $$$$     $$$  s  s$           s$$$     $$$ $$$$s`$$s' by 
$$$$'       `$$s $$     $$$s $$$$$       ..sSb $$     $$$      s$`$s panasync
$$$'         $$$s $    .$$$$ `$$$$     d$$$$$$ $$$    $$$    .$'  `$s.
$$$s.      .s$$$$ $$  .$$$$$  `$$$$s.   $$$$$$ $$$s   $$$   s$     `$$$$s
`$$$$Xavier$$$$$'s$$s $$$$$$s   `S$$sss$$$$$'s$$$$$  s$$$ s$$s      `$$$'

Last Updated: Fri Mar  26 16:50:22 EDT 2004


The Offical BitchX FAQ is now online.   Please visit http://faq.bitchx.org/


There are many #BitchX channels on various IRC networks.  The only OFFICAL
BicthX support channel is #BitchX on the EFnet IRC network.  While other network's
#BitchX channels do provide support for BitchX, and do a good job at it, your source
for OFFICAL BitchX related information is *.bitchx.org sites and #BitchX on EFnet.

A copy of the FAQ in HTML format has been included with the documentation but
we cannot assure you that it will be up to date at all times.  Please visit the
websites and ask questions there before you come to IRC.

--- NEW FILE: BitchX.xpm ---
/* XPM */
static char *BitchX[] = {
/* width height num_colors chars_per_pixel */
"    32    32      203            2",
/* colors */
".. c #080808",
".# c #101010",
".a c #181818",
".b c #212121",
".c c #292929",
".d c #313131",
".e c #393939",
".f c #424242",
".g c #4a4a4a",
".h c #636363",
".i c #6b6b6b",
".j c #737373",
".k c #7b7b7b",
".l c #848484",
".m c #8c8c8c",
".n c #949494",
".o c #9c9c9c",
".p c #b5b5b5",
".q c #bdbdbd",
".r c #312929",
".s c #b5ada5",
".t c #adada5",
".u c #84847b",
".v c #cecebd",
".w c #a5a594",
".x c #949484",
".y c #c6c6ad",
".z c #9c9c84",
".A c #84846b",
".B c #212118",
".C c #525239",
".D c #181810",
".E c #636339",
".F c #7b7b39",
".G c #101000",
".H c #181800",
".I c #6b7339",
".J c #c6d663",
".K c #637300",
".L c #949c6b",
".M c #293100",
".N c #d6deb5",
".O c #adb58c",
".P c #a5ad84",
".Q c #8c946b",
".R c #737b52",
".S c #a5b55a",
".T c #bdd652",
".U c #212900",
".V c #425200",
".W c #637b00",
".X c #bdce7b",
".Y c #cee773",
".Z c #738431",
".0 c #94ad31",
".1 c #849c29",
".2 c #a5ce00",
".3 c #bdce84",
".4 c #526318",
".5 c #637b10",
".6 c #394a00",
".7 c #526b00",
".8 c #adb594",
".9 c #a5ad8c",
"#. c #a5c642",
"## c #526b08",
"#a c #4a6300",
"#b c #8cbd00",
"#c c #94c600",
"#d c #b5d65a",
"#e c #bde74a",
"#f c #a5ce39",
"#g c #9cce21",
"#h c #7ba508",
"#i c #7bad00",
"#j c #94ce00",
"#k c #9cad73",
"#l c #a5c65a",
"#m c #8cb531",
"#n c #425a08",
"#o c #395200",
"#p c #73a500",
"#q c #adde4a",
"#r c #ade731",
"#s c #84b521",
"#t c #4a6b08",
"#u c #213100",
"#v c #639400",
"#w c #84b529",
"#x c #6b9c10",
"#y c #395208",
"#z c #314a00",
"#A c #7b846b",
"#B c #73a521",
"#C c #294200",
"#D c #528400",
"#E c #639c00",
"#F c #9cde39",
"#G c #73a529",
"#H c #426b00",
"#I c #4a7b00",
"#J c #5a9400",
"#K c #73bd00",
"#L c #7bb529",
"#M c #527b18",
"#N c #213900",
"#O c #528c00",
"#P c #8cd631",
"#Q c #6bad18",
"#R c #848c7b",
"#S c #8cce42",
"#T c #84ce31",
"#U c #396b00",
"#V c #63bd00",
"#W c #84c642",
"#X c #6ba531",
"#Y c #081000",
"#Z c #4a9400",
"#0 c #7b8c6b",
"#1 c #7bb542",
"#2 c #102100",
"#3 c #5ab500",
"#4 c #7b8473",
"#5 c #397308",
"#6 c #84c652",
"#7 c #396318",
"#8 c #296300",
"#9 c #639442",
"a. c #7bc64a",
"a# c #294218",
"aa c #5a9c31",
"ab c #529429",
"ac c #317b00",
"ad c #73ad52",
"ae c #63ad39",
"af c #427b21",
"ag c #295210",
"ah c #214a08",
"ai c #215a00",
"aj c #63944a",
"ak c #6bb542",
"al c #214210",
"am c #8c9c84",
"an c #293921",
"ao c #6bad4a",
"ap c #63a542",
"aq c #081800",
"ar c #103100",
"as c #216300",
"at c #297b00",
"au c #6ba552",
"av c #4aa521",
"aw c #216b00",
"ax c #637b5a",
"ay c #4a9c29",
"az c #738c6b",
"aA c #84b573",
"aB c #6b9c5a",
"aC c #102908",
"aD c #104200",
"aE c #428431",
"aF c #216310",
"aG c #104a00",
"aH c #6b8c63",
"aI c #426b39",
"aJ c #527b4a",
"aK c #083900",
"aL c #e7efe7",
"aM c #adb5ad",
"aN c #737b73",
"aO c #5a635a",
"aP c #424a42",
"aQ c #6b7b6b",
"aR c #395239",
"aS c #397b39",
"aT c #081808",
"aU c #000800",
"aV c #ced6d6",
"aW c #737b7b",
"aX c #4a5252",
"aY c #424a4a",
"aZ c #394242",
"a0 c #101818",
"a1 c #94a5ad",
"a2 c #a5b5bd",
"a3 c #9ca5ad",
"a4 c #5a636b",
"a5 c #a5adb5",
"a6 c #636b73",
"a7 c #4a525a",
"a8 c #081829",
"a9 c #737b8c",
"b. c #8c94ad",
"b# c #848ca5",
"ba c #737b94",
"bb c #7b7b84",
"bc c #52525a",
"bd c #5a5a63",
"be c #42424a",
"bf c #6b6b7b",
"bg c #73738c",
"bh c #000008",
"bi c #000000",
/* pixels */
"aOaO.g.g.g.g.g.g.g.g.g.g.g.g.g.g.g.g.g.g.g.g.g.g.g.g.g.g.g.g.g.g",
"aOaO.g.g.g.g.g.g.g.g.g.g.g.g.g.g.g.g.g.g.g.g.g.g.g.g.g.g.g.g.g.g",
".h.h.dbibibibibi.....#.#.B.b.r.d.f.f.gaXaXaXbeaZ.r.r.b.B.D.#.e.m",
".h.h.ebibibibibi.....#a0.b.b.d.dbebebcbdbdbcaY.f.d.d.b.B.D.#.f.o",
".h.h.ebibibibibi.....#.a.b.c.d.ebcbcbgbaa9bfbcaX.e.e.b.b.D.D.f.o",
".h.h.ebibibibibi.....#a0.b.c.e.fbdbdb#a1b.baa4aX.e.e.b.b.D.#.f.o",
".h.h.ebiaX.l.k.k.k.k.k.k.k.k.f.fa6a6aVaL.l.lbb.k.k.k.k.k.kaO.f.o",
".h.h.ebi...i.l.l.l.l.l.l.l.l.iaZbfbfaVaM.k.u.l.l.l.l.l.k.i.a.f.o",
".h.h.ebibibi.f.l.l.l.l.l.l.l.k.la7a7.u.k.l.l.l.l.l.l.l.g.#.#.f.o",
".h.h.ebibibi.f.l.l.l.l.l.l.l.k.la7a7.u.k.l.l.l.l.l.l.l.g.#.#.f.o",
".h.haRbibibibibi.k.k.k.k.k.j.j.j.j.j.j.j.j.k.k.k.k.k.a.a.#...f.o",
".h.haSbibibibibi.l.laWaN.j.j.j.j.j.j.j.j.j.j.k.k.k.k.aa0.#...f.o",
".h.hayaGaUbibibiaTaTaeapaHaHaoauaNaN.j.j.j.j.j.ja#a#aFal....aP.o",
".h.hah#2aDaUaUaU#2#2aq#Yadajalal#4#4aNaNaQaQaN.kagagarahaT..aI.o",
".h.hbibi#3atasaw#N#N#i#h#T#QbibiaBaBakaaafafaeaf#I#Ibi#HacasavaA",
".h.hbibi.Ubibi#Y#8#8#Y#Y#Q#2bibi#1#1aCbibibiaqaD#D#Dbi.MaUbi#2aa",
".h.hbibi#c#p.Vbi#J#Jbibi#r#gbibi#s#sbi#n#.#f#b#b#J#Jbi.6.2.Wbibi",
".h.hbibi#c#p.Vbi#J#Jbibi#r#gbibi#s#sbi#n#.#f#b#b#J#Jbi.6.2.Wbibi",
".h.hbibibibibibi#p#pbibi#q#mbibi#r#rbibiaUbibibi#J#Jbi#z#U#Hbibi",
".h.hbibi.Ubibi#Y#I#Ibibi#l#lbibi#q#q.Hbibibi#Y#n#a#abi#z#z#obibi",
".h.h.1.V.V.7.K.V#A#A.S.S.z.w.X.Y.N.N.3.J#d.T.S.L.R.R.V.M#Y.U.1#k",
".h.h.Zbi.G.G.G#Y.u.u#R.x.o.w.s.y.o.o.q.8.9.zam.m.u.u#Y#Ybi#Y.I.o",
".h.h.Cbibibibi.f.j.j.l.l.n.oaM.obibi.paM.o.n.l.l.j.j.bbibibi.f.o",
".h.h.ebibibi.d.l.j.jbb.l.m.n.t.lbibi.maM.n.m.l.k.j.j.j.#bibi.e.o",
".h.h.ebibi.i.j.j.j.j.k.k.l.m.hbibibi.b.l.m.l.k.k.j.j.j.j.ebi.e.o",
".h.h.ebibi.i.j.j.j.j.k.k.l.m.hbibibi.b.l.m.l.k.k.j.j.j.j.ebi.e.o",
".h.h.e.d.m.m.m.m.l.l.l.l.l.hbibibibibibi.l.l.l.l.l.l.m.m.l.m.f.o",
".h.h.e.d.e.e.e.e.e.e.e.e.f.abibibibibibi.d.f.e.e.e.e.e.e.e.eaO.o",
".h.h.ebibibibibibibibibi...abibibibibibibibibibibibibibibibi.e.o",
".h.h.ebibibibibibibibibibibibibibibibibibibibibibibibibibibi.e.o",
".h.h.ebibibibibibibibibia8bibibibibibibibibibibibibibibibibi.f.o",
".h.haM.p.p.p.p.p.p.p.p.p.p.p.p.p.p.p.p.p.p.p.p.p.p.p.p.p.p.p.p.t"
};

--- NEW FILE: BitchX.sites ---
    .sssSS$$s.s$$$$$$ $$sss..   s$$$^`$ss.   $$$$$s s$$$$  .s$$$$$s   s$s
 .$$$$$'  `$$$ $$$$$$ $$$$$$$$$s $$'   `$$$$s $$$'   `$$$  $$$$$$$'  s$$'
s$$$$'      `$s $$$$ $$' $$$ $$$ $      d$$$$s $$     $$$   `$$$$'  s$$'
$$$$$sss..ssS$'s$$$'s$' .$$' `$$ $     d$$$$$'s$$sssss$$$ $$$s`$$  s$'
$$$$$$$^^^^$$s $$$$     $$$  s  s$           s$$$     $$$ $$$$s`$$s' by 
$$$$'       `$$s $$     $$$s $$$$$       ..sSb $$     $$$      s$`$s panasync
$$$'         $$$s $    .$$$$ `$$$$     d$$$$$$ $$$    $$$    .$'  `$s.
$$$s.      .s$$$$ $$  .$$$$$  `$$$$s.   $$$$$$ $$$s   $$$   s$     `$$$$s
`$$$$Xavier$$$$$'s$$s $$$$$$s   `S$$sss$$$$$'s$$$$$  s$$$ s$$s      `$$$'

Last Updated: Fri Mar  26 16:52:21 EDT 2004

The OFFICAL BitchX sites are listed below.  Only sites listed here can
be considered 'trusted' sources of information about BitchX.

Use any other sites at your own risk, we can not guarantee the accuracy
or security of files obtained from sites other than the ones listed below.

http://www.bitchx.org/
http://faq.bitchx.org/
http://scripts.bitchx.org/
http://bugs.bitchx.org
http://forums.bitchx.org

ftp://ftp.bitchx.org/
ftp://ftp.cyberpunkz.org/


--- NEW FILE: ircII.servers ---
[EFnet US]
irc.weblook2k.com
irc.vrfx.com
irc.umn.edu
irc.umich.edu
irc.secsup.org
irc.qeast.net
irc.nac.net
irc.isprime.com
irc.easynews.com
irc.desync.com
irc.blessed.net
irc.aloha.net

[EFnet Canada]
irc.torix.ca
irc.mpls.ca
irc.avalonworks.ca
irc.arcti.ca

[EFnet Europe, Middle East, Asia]
irc.inter.net.il
irc.inet.tele.dk
irc.homelien.no
irc.hemmet.chalmers.se
irc.efnet.nl
irc.du.se
irc.dkom.at
efnet.skynet.be
efnet.demon.co.uk
efnet.cs.hut.fi

[DALnet]
irc.dal.net

[IRCnet]
ircnet.netvision.net.il
ircnet.easynet.co.uk
ircnet.demon.co.uk
irc.xs4all.nl
irc.tokyo.wide.ad.jp
irc.swipnet.se
irc.stealth.net
irc.skynet.be
irc.sci.kun.nl
irc.ru
irc.pvv.ntnu.no
irc.powertech.no
irc.oulu.fi
irc.netsurf.de
irc.media.kyoto-u.ac.jp
irc.ircnet.net
irc.ircnet.dk
irc.flashnet.it
irc.excite.it
irc.datacomm.ch
irc.cs.hut.fi
fu-berlin.de

[QuakeNet]
wineasy.se.quakenet.org
whole.ny.us.quakenet.org
tiscali.dk.quakenet.org
splatterworld.de.quakenet.org
snoke.nl.quakenet.org
port80.se.quakenet.org
oslo.no.quakenet.org
mediatraffic.fi.quakenet.org
demon.uk.quakenet.org
barrysworld.uk.quakenet.org

[Undernet US, Canada]
washington.dc.us.undernet.org
sanjose.ca.us.undernet.org
montreal.qu.ca.undernet.org
mesa.az.us.undernet.org
mclean.va.us.undernet.org
fairfax.va.us.undernet.org
atlanta.ga.us.undernet.org

[Undernet Europe, Middle East, Asia]
surrey.uk.eu.undernet.org
stockholm.se.eu.undernet.org
milan.it.eu.undernet.org
london.uk.eu.undernet.org
helsinki.fi.eu.undernet.org
geneva.ch.eu.undernet.org
diemen.nl.eu.undernet.org
amsterdam.nl.eu.undernet.org

[UniBG]
irc.unibg.org
irc.spnet.net
irc.otel.net
irc.omega.bg
irc.nbu.bg
irc.lt-tech.org
irc.lirex.com
irc.langame.net
irc.comnet.bg
irc.chatbg.net

[LinkNet]
se.link-net.org
irc.mindimage.net
irc.link-net.org
irc.lagged.no
irc.kinexuseurope.co.uk
irc.firelab.net
irc.de.link-net.org
irc.bsdlink.net




More information about the dslinux-commit mailing list