BitchX is fairly simple to install, if your OS is supported you will need to do the following:
% gunzip ircii-pana-xx.tar.gz
% tar xvf ircii-pana-xx.tar
% cd BitchX
% ./configure
% make
% make install (only as root to install globally)
If the you have any problems in the compilation process of BitchX. If you gather as much information about the error (output from make) and join the BitchX support channel on EFnet, #BitchX, or email the author at the following edwac@sk.sympatico.ca. Bug reports can be sent exactly in the same way. You might want to check the INSTALLATION file included in the source code for any common compile problems that have been reported. This file also includes details of how to use TCL and the more advanced features of BitchX.
BitchX has full tcl support and is constantly being updated with more features. To compile BitchX with tcl support you will need to obtain a binary file of tcl.o for your operating system. You can always get the latest copy of these from #BitchX on EFnet, or the ftp sites. You will need to place the binary in BitchX/source, then after running the GNU configure script you can edit your ../Makefile and uncomment the following lines:
TCLINC = -I/usr/include TCLLIB = -L/usr/lib -ltcl -lm TCL = -DWANT_TCL # TCL_SRCS = tcl.c TCL_OBJS = tcl.o
Now when you run GNU make, BitchX will be compiled with tcl support. You can load a tcl file with /tcl -file /patch/file.tcl. Tcl.c is not included in the standard BitchX package, this file is only available to the current BitchX developers who will make binaries available.
Starting BitchX is as simple as typing BitchX at a command prompt or by clicking on a icon. BUT there are some options which you might want to use.
Usage: BitchX [switches] [nickname] [server list] The [nickname] can be at most 9 characters long The [server list] is a whitespace separate list of server name The [switches] may be any or all of the following -H <hostname> uses the virtual hostname if possible -c <channel> joins <channel> on startup -b load .bitchxrc or .ircrc after connecting to a server -p <port> default server connection port (usually 6667) -f your terminal uses flow controls (^S/^Q), so BitchX shouldn't -F your terminal doesn't use flow control (default) -d runs BitchX in "dumb" terminal mode -q does not load ~/.ircrc -r file load file as list of servers -n nickname nickname to use -a adds default servers and command line servers to server list -x runs BitchX in "debug" mode -v tells you about the client's version -B force BitchX to fork and return you to shell -l <file> loads <file> in place of your .ircrc -L <file> loads <file> in place of your .ircrc and expands $ expandos
BitchX supports all of the standard commands that you will be used to in most other unix clients such as ircii, epic, scrollz. Below is a list of common commands that will be probably used a lot.
BitchX.reasons - Random kick messages BitchX.quit - Random quit messages BitchX.help - Help file
All these files should be copied to the  /.BitchX directory.
One of the most frequently asked questions is how do get I get rid of * I'm too lame to read BitchX.doc * when I do a whois on myself. Well the answer to this is quite easy you need to set up some variables. The following variables can be set:
Variable Value IRCNICK - "nickname" Sets the default nickname to use. IRCNAME - "username" Sets the default whois username, aka the * I'm too lame to read BitchX.doc * IRC_HOST - "hostname" Sets the virtual hostname, don't worry about this unless you need it. IRCSERVER - "server" Sets the default server to use. IRCPORT - "port" Sets the default port to use. IRCUMODE - "modes" Sets the default usermode. IRCRC - "filename" Sets the filename to use in place of irc-rc
To set up these variables will depend on the type of shell you use in bash you would type:
% export VARIABLE="value"
In csh/tcsh the command you type would be:
% setenv VARIABLE "value"
If you do not use one of these shells, I surgest you type man "yourshell" to find out how you set up a variables.
First of all to make sure BitchX work properly in XWindows you will need to obtain rxvt or Eterm and use a vga font like vga11x19. If you use rxvt you will need to start it with the options "-bg black -fg white -fn vga11x19". Its counterpart Eterm has a .Eterm/MAIN file that you can set the colors and font in. If the function keys don't work, you may need to add this to the  /.bitchxrc file:
/bind meta3-1 chelp /bind meta3-2 CHANNEL_CHOPS /bind meta3-3 CHANNEL_NONOPS /bind meta3-4 CDCC_PLIST /bind meta3-5 DCC_PLIST /bind meta3-6 DCC_STATS
bitchxrc and ircrc are both variants of the same thing, a file loaded up by BitchX automatically. What are the differences? .ircrc - this is loaded by all ircII clients, only put stuff that will work with base ircII scripting here. Also, this is loaded upon connecting to a server. .bitchxrc - this is loaded as soon as BitchX starts. Put all BitchX-specific scripting commands here.
bxglobal is simply more than a global .bitchxrc file.