Version 2.0 of rxIRC (By Lynx (244661 at DOLUNI1) 1993)

00readme

@@ -0,0 +1,7 @@
+From: Carl von Loesch <Carl.von.Loesch@arbi.informatik.uni-oldenburg.de>
+To: rxirc-l@vmtecqro.qro.itesm.mx (The rxIRC List),
+        operlist@eff.org (IRC Operchaos List)
+Subject: rxIRC 2.0 ready to go - FTP admins invited to copy/mirror!
+Date: Mon, 14 Jun 93 15:57:16 CES
+
+I am hereby releasing rxIRC 2.0. rxIRC is the IRC client for IBM VM systems.

action.helpirc

@@ -1,4 +1,4 @@
-.cm last change by lynx -- january, 1992
+.cm last change by lynx -- may 93
  
                  _______
                *|^^^^^^^|*           The Internet Relay Chat program
@@ -18,7 +18,7 @@ ACTION commands:
  You'll find out by experimenting.
  
  The commands at disposition in the present rxIRC version are:
-   BOW, COMFORT, CUDDLE, DANCE, GIGGLE, GRIN, HUG, LAUGH
+   APPLAUD, BOW, COMFORT, CUDDLE, DANCE, GIGGLE, GRIN, HUG, LAUGH
    NOD, SHRUG, SIGH, SMile, THank, WAVE, WINK, YAWN
  
  You should know that you can also produce your own message lines

custom.helpirc

@@ -10,16 +10,19 @@
                   *** How to customize rxIRC ***
  
  
-The IRC PROFILE startup file:
+The PROFILE RXIRC startup file:
-  This file should contain a series of lines that are executed by
+| This file should contain a series of lines that are /source'd by
-  rxIRC as if you would type them in as soon as you get connected to
+| rxIRC as soon as you get connected to the first server. You could
-  a server. You could for instance do "/join #fun" or "/who bunny"
+| for instance do "join #fun" or "who bunny", probably you will
+| want to set up some aliases. See /source for more.
+| The file IRC PROFILE is obsolete. For a conversion you have
+| to rename it and remove all the command characters (the slashes).
  
 Namesfile settings:
   rxIRC gets your default nickname and full name from your namesfile
   unless otherwise specified in the command line. You can also set
   a 'motto' line by adding a :motto tag to your self-entry in your
-  namesfile which will be displayed when VERSION requests are sent
+  namesfile which will be displayed when USERINFO requests are sent
   to you while you are ircing with rxIRC.
  
 Environment settings:
@@ -28,25 +31,30 @@ Environment settings:
   IRCNAME and IRCPORT. rxIRC uses 'SELECT CENV' for compatibility with
   other IRC programs.
  
-Defaults in the RXIRC NAMES file:
+The RXIRC PFKEYS file is obsolete. You can use the 'PF' commands
-  Some defaults for the rxIRC program are defined here:
+| from PROFILE RXIRC now.
-    server:           the Internet address of an irc server
+ 
-    port:             the TCP/IP port it runs on, usually 6667
+Defaults in the RXIRC NAMES file (the rxIRC configuration file):
-    timeout:          when rxIRC should give up on connections
+    server:           The internet address of an IRC server
-    logging:          make it ON or OFF
+    port:             The TCP/IP port it runs on, usually 6667
-    quiet_ignore:     usually OFF
+|   browser:          Name of a command good for showing files.
-    loud_beeps:       ON only when a BEEP MODULE is available.
+|                     Typically BROWSE, but if that's not there try XEDIT.
-    show_numbers:     ON shows the reply numbers of server replies, for freaks.
+|   timeout:          Not used anymore, you can remove it
-    list_all:         show also channels without topic in /list, i use OFF.
+    logging:          Set it to ON or OFF for default logging
-    beep_char:        the character that gets translated into a beep and back.
+    quiet_ignore:     Usually OFF
-    highlight_char:   the char that gets translated into an inverse on ircII.
+    loud_beeps:       Switch it ON only when a BEEP MODULE is available.
+    show_numbers:     When ON, rxIRC shows the numerics of IRC server replies
+    list_all:         Show also channels without topic in /list
+|   beep_char:        The character that gets translated into a beep and back.
+|   bold_char:        If you define this one, you can make 'bold' messages
+|                     by inserting this character in your messages. They
+|                     will appear hilighted on rxIRC and bold on ircII 
+|                     clients (at least)
+|   highlight_char:   Not used anymore
+|   show_time:        When the current time will be displayed on the
+|                     screen.  Choices are 0 (never), 10 (every ten
+|                     minutes), 20 (every 20 minutes), 30 (every 30
+|                     minutes), and 60 (every 60 minutes).
  
   You might choose to copy this file onto your disk to be able to
   modify the values.
- 
---
-You have 10069612 experience points, 99159963 gold coins, 9127 spell points.
-You also have 9999 hit points out of 9999.
-Strength: 966;  Dexterity: 939;  Intelligence: 957;  Constitution: 948.
-Your age: 50 days 15 hours 37 minutes 32 seconds.
- 

etiq.helpirc

@@ -1,84 +0,0 @@
-/************************************************************************
- *   IRC - Internet Relay Chat, doc/etiquette
- *   Copyright (C) 1990, Lea Viljanen and Ari Husa
- *
- *   This program is free software; you can redistribute it and/or modify
- *   it under the terms of the GNU General Public License as published by
- *   the Free Software Foundation; either version 1, or (at your option)
- *   any later version.
- *
- *   This program is distributed in the hope that it will be useful,
- *   but WITHOUT ANY WARRANTY; without even the implied warranty of
- *   MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
- *   GNU General Public License for more details.
- *
- *   You should have received a copy of the GNU General Public License
- *   along with this program; if not, write to the Free Software
- *   Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
- */
- 
-HOW TO BEHAVE ON IRC
- 
-Authors:      Lea Viljanen (LadyBug)  viljanen@kreeta.helsinki.fi
-              Ari Husa     (luru)     so-luru@tolsun.oulu.fi 
- 
- 
-1) Language
- 
-   The most widely understood and spoken language on IRC is English. 
-However! As IRC is used in many different countries, English is by
-no means the only language. If you want to speak some other language
-than English (for example with your friends), go to a separate channel
-and set the topic (with /topic) to indicate that. For example
-   /topic Finnish only!
-would mean that this channel would be reserved for Finnish discussion.
-On the other hand, you should check the topic (with /list command) 
-before you move to a channel to see if there are any restrictions about 
-language.
-   On a channel not restricted by /topic, please speak a language
-everybody can understand. If you want to do otherwise, change channels
-and set the topic accordingly.
- 
- 
-2) Hello/Goodbye
- 
-   It's not necessary to greet everybody on a channel personally.
-Usually one "Hello" or equivalent is enough. And don't expect everybody
-to greet you back. On a channel with 20 people that would mean one
-screenful of hellos. It's sensible not to greet, in order not to be rude
-to the rest of the channel. If you must say hello, do it with a private /msg.
-The same applies to goodbyes.
- 
- 
-3) Discussion
- 
-   When you come to a new channel it's advised you to listen
-for a while to get an impression of what's discussed. Please feel free
-to join in, but do not try to force your topic into the discussion
-if that doesn't come naturally.
- 
- 
-4) {}|[]\
- 
-   IRC has quite a lot of people from Scandinavian countries,
-the above characters are letters in their alphabet. This 
-has been explained on IRC about a thousand and one times, so
-read the following, do not ask it on IRC:
- 
-   {     is an A with 2 dots over it
-   }     is an A with a small circle above it
-   |     is either an O with 2 dots over it or an O with a dash (/) through it
-   [, ], and \ are the preceding three letters in upper case.
- 
-   There are a lot of people from Japan as well, who use Kanji characters
-which may look quite exotic as well. As I don't know Kanji I don't
-even try to explain any of the characters.
- 
-5) ATTENTION!
- 
-   Remember, people on IRC form their opinions about you only by 
-your actions, writings and comments on IRC. So think before you type.
-Do not "dump" to a channel or user (send large amounts of unwanted
-information). This is likely to get you /kicked off the channel or
-/killed off from irc. Dumping causes network 'burbs', connections going
-down because servers cannot handle the large amount of traffic any more.

faq.helpirc

@@ -1,28 +1,32 @@
 Frequently asked questions:
 --------------------------
-1.  Why can't rxIRC have /alias and /on and /notify and everything else
+What am I supposed to write into the :server field in RXIRC NAMES?
-    that ircII has?
+ 
+  You don't have a server? If you're in the US then Trillian
+  (hrose@eff.org) will most probably be able to tell you the nearest
+  server to you. You can however connect to IRC through an open server
+  like irc.mit.edu (18.70.0.224), fairhope.andrew.cmu.edu (128.2.11.213)
+  magpie.ee.su.oz.au (129.78.13.28) or ucsu.colorado.edu (128.138.129.83)
+| and then ask operators for the nearest server to you.
+  You can also examine the /links list, but geographical vicinity
+  usually is not network vicinity!
+ 
+|Why can't rxIRC have /on and /notify and everything else
+|that ircII has?
  
   Because ircII is a giant program that a lot of people have worked on
   to be able to do all of that. rxIRC is a relatively little program
   which I also want to stay that way, or it might get unpleasantly
   slow in execution!
+|
+|Strange says:
+| There is no /on because no one wants to code it.  None of the people
+| who have worked on rxIRC NEED or WANT /on.  :P
+|
+| Concerning /notify:    Use a /note server!  :)
  
-  I am sure that /alias and /on are functionalities that take a lot
+Why when I do something outside of rxIRC with /exec, or simply read
-  of time to develop and most of all consume to much speed. And they
+the /help files, the server signs me off?
-  would look really ugly in the sourcecode. If you just would learn
-  a little REXX you'd see that you can easily add commands into the
-  EDIT: procedure and add hooks into the PARSE: procedure. You don't
-  need any /on or /alias!
- 
-  Concerning /notify, this could even be done, though it's a little
-  tough to simulate a timer when REXTCPIP doesn't offer it. I might
-  be inclined to do it, but I don't even use rxIRC myself, so why
-  should I spend serious time on it?  If you care, go ahead and do
-  it yourself. Then send a copy of it to me, so I can release it.
- 
-2.  Why when I do something outside of rxIRC with /exec, or simply read
-    the /help files, the server signs me off?
  
   In this case the evil ping goblin has bitten you. A particularity of the
   IRC protocol is that the server expects your client program to reply to
@@ -30,22 +34,30 @@ Frequently asked questions:
   idle. When you start a command with ! or /exec, rxIRC is not able to
   reply to the PING and the server closes the connection on you. Poof.
  
-3. You have a bug, "/who -h *.il" doesn't work!
+You have a bug, "/who -h *.il" doesn't work!
  
   No, I don't have such a bug. The "-h" and "-s" options are specific
   to ircII. They are NOT standard. It is the normal and natural way
-  to do it simply with "/who *.il"
+  to do it simply with "/who *.il". Or what about trying /local.
  
-4. When I use one of the new action commands on a channel, like /smile
+When I use one of the new action commands on a channel, like /smile
-  I get a lot of error messages.
+I get error messages.
  
-  The CTCP ACTION protocol is still rather new, not everyone likes, not
+| There are controverse notions of the ethics of the CTCP ACTION protocol.
-  everyone supports it, and most of all, a lot of people do not have up
+| I think it's a valid alternative form of communication and should be
-  to date IRC programs. When you get such error messages better not use
+| supported, but since I invented it I might be biased. Well some IRC
-  the commands on those channels. On other channels you might find people,
+| client programmers insist on not supporting this protocol and return
-  who have newer clients, and you'll be able to communicate with the new
+| all sorts of funny messages. Eventually avoid using these commands
-  commands.
+| on channels where people's clients answer with sarcastic comments.
+ 
+rxIRC crashes and then no communication software (like CHAT) works
+anymore!
+
+| rxIRC should not crash, if it does please report that to me.
+| To unlock your machine in such a situation it is not necessary to
+| re-IPL it, instead just do "NUCXDROP REXXWAIT". "NUCXMAP" shows
+| what so-called nucleus extensions are loaded in your machine.
 
 You still have a question?
-Write mail to 244661 at DOLUNI1 (.bitnet) or to
+Write mail to 'loesch@informatik.uni-oldenburg.de' (internet).
-'loesch@informatik.uni-oldenburg.de' (internet).
+or to '244661 at DOLUNI1' (bitnet)

intro.helpirc

@@ -0,0 +1,350 @@
+                       INTERNET RELAY CHAT
+ 
+ 
+Author:  Robert D. Blais
+Email:  <IO00058@Maine.maine.edu>
+        <IO00058@Maine.Bitnet>
+Revised:  27 February 1993
+Version: 1.10
+ 
+PURPOSE:  This document attempts to explain, in simple terms,
+what IRC is and in general, how it is used. It is intended to
+supply information for new users not familiar with IRC and to
+serve as a reference for experienced users.
+     Since there are many different programs on several different
+operating systems, client-specific information has been left out.
+Users should refer to the documentation that came with their IRC
+program for information specific to using that client.
+     Users may also wish to read the author's document "Standard
+IRC Commands" for information about the commands mentioned in
+this document.
+ 
+CREDITS:  The information contained in this document has been
+culled several sources, including the alt.irc group in Usenet
+news and from the author's own experience using IRC.  In
+addition, the following documents proved invaluable in the making
+of this document:  "Alt.irc.faq" by Helen Rose <hrose@eff.org>,
+"Internet Relay Chat, a real-time conversational system" by Karl
+Kleinpaste <karl@cis.ohio-state.edu>, and "How To Behave on IRC"
+by Lea Viljanen <viljanen@kreeta.helsinki.fi> and Ari Husa
+<so-luru@tolsun.oulu.fi>.  Thanks to Kelly Derek Deyoe
+<kd2a+@andrew.cmu.edu> for providing a list of countries and
+their domain extensions.  Special thanks to Carl "LynX" von Loesch
+for his help and suggestions.
+ 
+I. HISTORY
+ 
+     Internet Relay Chat (IRC) was originally written by Jarkko
+Oikarinen <jto@tolsun.oulu.fi> in 1988 as a replacement for the
+Unix "Talk" program.  It's purpose is to allow multiple users to
+converse in real-time over the collection of networks known as
+Internet.  It is based on the functionality of the Bitnet Relay
+system but that functionality has been greatly expanded.
+     From it's humble beginnings in Finland, IRC grew to become
+the largest international, relayed conferencing system in the
+world.  It is available in over 20 countries around the world and
+has been host to over 1000 users at one time!  Countless thousands
+of people, from college students to business executives have used
+IRC and new users sign-on every day.
+     The Internet is primarily for academic use.  IRC is a
+communications layer of internet, and as such, it's main purpose
+is academic use.  Many people depend on it as a tool for
+exchanging information with colleagues, business associates and
+fellow researchers.
+ 
+II. CHANNELS
+ 
+     IRC is divided up into virtual spaces called channels.  A
+channel is a gathering place where people with a common interest
+can get together and discuss whatever that interest may be.  A
+channel does not exist until someone joins it and ceases to
+exist when the last person leaves it.
+ 
+A. Channel Names
+ 
+     All channels on IRC have names.  A channel name can be just
+about any single "word" of text preceded by a pound sign (#).
+For example, #123, #My_channel, and #$$$ are all valid channel
+names.  Examples of popular channels on IRC include #hottub,
+#initgame, and #hotsex.
+ 
+B. Creating A Channel
+ 
+     To create a channel, simply join it either with the /join
+or /channel command.  For example, to create the channel #Test
+you would type /join #Test.
+ 
+C. Leaving A Channel
+ 
+     To leave a channel, issue the /part command.  For example,
+to leave #Test you would type /part #Test.  Some clients will
+automatically issue /part for you if you use the /channel
+command, so check your program's documentation.
+ 
+D. Multiple Channels
+ 
+     Most IRC client programs allow you to be on several channels
+at once.  Check your client's documentation for specific
+information on using multiple channels.  Also, look for
+information on the /, /msg, and /query commands.
+ 
+E. Channel Operators
+ 
+     The first person to join a channel is known as the Channel
+Operator (ChanOp) and can determine certain aspects of the
+channel, such as the number of people allowed on the channel and
+whether the channel is public, private, secret, or invite-only.
+A ChanOp can also delegate ChanOp privileges to other users on
+the channel.  Look for information on the /mode command for
+specifics about channel modes and ChanOp powers.
+ 
+III. NICKNAMES
+ 
+     All IRC users are identified by unique nicknames.  Duplicate
+nicknames are not allowed by the IRC servers.
+ 
+A. Changing Nicknames
+ 
+     By default your nickname is your userid, but may be changed
+with the /nick command.  Many clients also allow you to specify a
+default nickname that will be used whenever you sign-on to IRC.
+Check your client's documentation for specifics about setting a
+default nickname.
+ 
+B. Nickserv
+ 
+     Many people register their nicknames with an on-line service
+called Nickserv.  If you choose a nickname that is registered to
+someone else, you will get a message from Nickserv telling you
+who it is registered to.  If you get such a message, pick a new
+nickname.  It is considered very rude to use someone else's
+nickname and may cause confusion when other users mistake you for
+their friend.
+     For nickname registration information type the command
+/msg nickserv@service.de help.  When you register a nickname,
+Nickserv will ask you for a password. DO NOT USE YOUR LOGIN
+PASSWORD.  IRC protocols are not completely secure and other
+users may be able to get your Nickserv password.  Also, REMEMBER
+YOUR NICKSERV PASSWORD.  You may need it if you ever want to
+change your registered nickname or add a new host site to your
+access list.
+ 
+IV.  IRC OPERATORS
+ 
+     The IRC Operators (IRCOps) are the people who maintain IRC.
+They keep the servers running and up to date, keep the links
+connected and routed properly, they answer questions from the
+users, and they remove offensive users by way of the /kill
+command.  IRCOps are indicated by an asterisk (*) next to their
+nickname in /who and by the line "<nick> has a connection to the
+Twilight Zone." in /whois.
+     The best way to get help or information from IRCOps is to
+join the IRCOp channel #Twilight_zone.  Once you are on the
+channel, state your problem or question in a brief, specific,
+polite manner and wait for a reply.  Usually you'll get a
+response within a few minutes, but since many of the IRCOps have
+responsibilities apart from IRC, they aren't always immediately
+available.  If you don't get a reply in a reasonable amount of
+time, try again later.
+ 
+V. MESSAGES
+ 
+     There are generally four types of messages you will see
+while using IRC.  The four types are informational messages,
+public messages, private messages, and notices.  Some clients may
+also have a fifth type that gives information about things
+happening within the program, such as when you add a user to the
+/ignore list, but these messages are not normally sent over IRC.
+ 
+A. Informational messages.
+ 
+     Informational messages let you know something in the IRC
+environment has changed.  When someone joins or leaves your
+channel, changes the channel mode or topic, changes their
+nickname, or makes some other such change you will see a message
+informing you of the change.  The format of the message may vary
+depending on what client you are running, but in general it will
+look something like the following:
+ 
+*** Bub joins channel #hottub
+*** Mode change: Hoser sets #hottub +o Bub
+ 
+B. Public Messages.
+ 
+     Public messages are seen by everyone on the channel.
+Everything you type to a channel shows up as a public message
+with your nickname and the channel name displayed in angle
+brackets before the message.  A public message looks like the
+following:
+ 
+<Bub:#hottub> Hello world!
+  or
+<Bub> Hello world!
+ 
+C. Private Messages.
+ 
+     Private messages are generally only seen by the person who
+they are sent to.  The /msg and /query commands are used to send
+private messages.  Private messages are displayed with the
+sender's nickname between asterisks.  A private message would
+look like the following:
+ 
+*Bub* Thanks for Opping me, Hoser.
+ 
+D. Notices
+ 
+     Any automatic response, such as server messages, CTCP
+(client to client protocol) replies, and robot replies MUST be in
+the form of a notice.  Users can also send notices with the
+/notice command, but this is not generally necessary.  A notice
+will generally be shown with the sender's nickname and channel
+between dashes and might look like the following:
+ 
+-Bubserv:#hottub- Bub sends a beer to Hoser.
+-Bubserv:#hottub- /msg Bubserv help  for help on using Bubserv.
+ 
+VI. SERVERS
+ 
+     IRC servers are programs that relay the messages and
+commands that you type to other servers and users on the network.
+When you first compile or use an IRC program, you will probably
+have to give it a server to use.  You should normally use the
+closest (network-wise) server to you.  However, some servers
+limit what hosts are allowed to connect to them.
+     Lists of servers are frequently posted in the Usenet news
+group alt.irc.  If you don't have access to that group and can't
+find a server, try one of the following servers and once you get
+on, ask an IRCOp which server in your area you should use.
+ 
+Open servers by country:
+     Australia:    coombs.anu.edu.au
+     Canada:       ug.cs.dal.ca
+     Finland:      nic.funet.fi
+     Germany:      irc.informatik.tu-muenchen.de
+     Netherlands:  fysak.fys.ruu.nl
+     U.S.A.:       csd.bu.edu
+                   ucsu.colorado.edu
+ 
+     Information about a specific server can be obtained by using
+the /admin, /info, /motd, and /version commands.  If you have a
+problem with a particular server the /admin command will give you
+the email address of the person(s) in charge of it.  The other
+commands give you information about the server itself, such as
+the software version and the MOTD (Message of the Day).
+ 
+VII. BEHAVIOR AND ETIQUETTE
+ 
+     IRC is a good place to learn about other people, places, and
+cultures, to exchange information and ideas, and to meet people.
+If everyone follows some basic, common-sense rules of behavior
+and etiquette, IRC can be an enjoyable and informative way to use
+some of your free time.
+ 
+A. Language
+ 
+     English is the most widely spoken language on IRC but it is
+not the only language.  Often the channel name or topic will give
+you some idea of the language spoken on that channel but this is
+not always the case.  A user's hostname extension usually gives
+an indication of where that user is from and thus, the language
+he or she is likely to speak.  For example, someone whose
+user@host name ends in .jp is most likely speaks Japanese, whereas
+someone whose user@host name ends in .fi most likely speaks
+Finnish.  A list of common domain extensions, by country, is shown
+below.
+ 
+ Country      Domain Extension
+Austria:            .at
+Australia:          .au
+Belgium:            .be
+Canada:             .ca
+Switzerland:        .ch
+Chile:              .cl
+Czechoslovakia:     .cs
+Germany:            .de
+Denmark:            .dk
+Spain:              .es
+Finland:            .fi
+France:             .fr
+Ireland:            .ie
+Israel:             .il
+Iceland:            .is
+Italy:              .it
+Japan:              .jp
+Korea:              .kr
+Mexico:             .mx
+Netherlands:        .nl
+Norway:             .no
+New Zealand:        .nz
+Poland:             .pl
+Sweeden:            .se
+Singapore:          .sg
+Taiwan:             .tw
+United Kingdom:     .uk
+United States:      .us
+South Africa:       .za
+Other:              .com  (Commercial business)
+                    .edu  (Educational institution)
+                    .gov  (Government organization)
+                    .mil  (Military installation)
+                    .org  (Non-profit organization)
+                    .net  (Network administration)
+ 
+     It is a good idea to do a /who on a channel before you join
+so you can get an idea of what language might be spoken on that
+channel. If the channel consists mostly of people from Finland
+and you don't speak Finnish, you probably won't find the channel
+very interesting.  Also, your own channel name or topic should
+indicate what language is spoken on your channel, especially if
+it is not English.
+ 
+B. Dumping and Flooding
+ 
+     Dumping large amounts of text or graphics to a channel or a
+user is considered rude and is not allowed.  It is a waste of
+bandwidth and can cause anyone on a slow modem connection to be
+jammed for several minutes. Also, the text or graphics that you
+find amusing is likely to be quite annoying to other users who
+are trying to carry on a conversation.
+ 
+C. Morality
+ 
+     Since IRC is composed of users from all over the world, with
+many different backgrounds, different levels of maturity, and
+different religious and moral standards, a good rule of thumb is
+think before you type.  If you wouldn't say something in front of
+your boss, teachers, parents, or in other social situations, you
+shouldn't say it on IRC.  By the same token, be tolerant of other
+users.  Not all of them have the same views and morals as you and
+what is offensive to you might not be to them.
+ 
+D. General Behavior
+ 
+     People on IRC have no other way of judging you than by your
+actions and messages.  Rude, obnoxious, and offensive behavior is
+not tolerated and may get you banned from a channel or /killed
+from IRC altogether.  If your offenses are great enough, your
+local system administrators may be notified and you may lose your
+computer account or face other disciplinary actions.
+     Not everyone using IRC is interested in chatting.  More
+specifically, not everyone on IRC is interested in chatting with
+YOU.  Some people use IRC as part of their normal work to be
+available to colleagues who might need to reach them quickly.
+Other people use IRC for discussion of certain topics of interest
+to them.  If you don't have anything to contribute to the topic
+on a particular channel, don't interrupt and try to start a new
+topic.  Start a new channel to discuss your topic.
+     If you send a message to someone or invite them to your
+channel, don't assume they are interested in talking to you.  If
+someone doesn't respond, they may be away from their terminal or
+may be too busy to reply.  If someone indicates that they aren't
+interested in talking to you, leave them alone.  Badgering
+someone or sending them unwanted messages wastes their time and
+yours.  You're better off finding someone else to chat with.
+ 
+--
+NOTE:  This document is hereby placed in the public domain.  If
+you copy it, please attribute the source.  If you modify it,
+please note who you are, what changes you made and the date of
+those changes in the document header.  Take the credit you
+deserve, but give credit where it is due.  Thanks.

manual.helpirc

@@ -1,287 +0,0 @@
-/************************************************************************
- *   IRC - Internet Relay Chat, doc/MANUAL
- *   Copyright (C) 1990, Karl Kleinpaste
- *
- *   This program is free software; you can redistribute it and/or modify
- *   it under the terms of the GNU General Public License as published by
- *   the Free Software Foundation; either version 1, or (at your option)
- *   any later version.
- *
- *   This program is distributed in the hope that it will be useful,
- *   but WITHOUT ANY WARRANTY; without even the implied warranty of
- *   MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
- *   GNU General Public License for more details.
- *
- *   You should have received a copy of the GNU General Public License
- *   along with this program; if not, write to the Free Software
- *   Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
- */
- 
-                                              Author: Karl Kleinpaste
-                                                      karl@cis.ohio-state.edu
-                                                Date: 04 Apr 1989
-                                   Last modification: 04 Apr 1989
- 
-			 INTERNET RELAY CHAT
-		  a real-time conversational system
- 
- 
-* 2: Entering Internet Relay Chat
- 
-Type `irc'.  If one wishes to be known by a nickname which is not
-one's login name, type `irc chosen-nickname' instead.
- 
-** 4.1: Nicknames
- 
-All users of irc are known to the system by a `nickname.'  By
-default, one's nickname is one's login name.  Nickname clashes are not
-allowed; this is enforced by the servers.  If one's intended nickname
-clashes with someone else as one enters chat, one will not be able to
-complete entry to irc until one changes one's nickname to something
-else.
- 
-** 4.2: Presence on a channel
- 
-Fundamental to the operation of irc is the concept of a channel.  All
-users are `on a channel' while inside irc.  One enters the `null
-channel,' channel 0, first.  One cannot send any messages while in
-channel 0 unless one has set up a private conversation in some way.
-The number of channels is essentially unlimited - whatever will fit in
-a 32-bit integer.
- 
-** 4.3: Types of channels
- 
-There are 3 channel types, with increasing levels of privacy afforded
-them.
- 
-*** 4.3.1: Public channels
- 
-Public channels are channels 1-999.  If one is on one of these
-channels, one can be seen by all other users.  Anyone can notice users
-on a public channel and join such a channel's conversation.
- 
-*** 4.3.2: Private channels
- 
-Channels 1000-up are called `private'  This means that, although
-anyone can see that one is using chat, no one can tell what channel
-one is using unless one is already on that channel with oneself.
-Since the number of potential channels is in the billions, this is
-quite some security - all one gives away is the acknowledgement that
-one is using chat.
- 
-*** 4.3.3: Secret channels
- 
-Negative channel numbers are called `secret'  While one is on a
-hidden channel, no one who is not on one's channel with oneself can
-even see that one is there.  One's name does not show up in a list of
-active users.  The only indication of one's presence is that, when
-entering chat, all new users are told that there are "N users on P
-servers."  If one checks on all users and finds less than N of them,
-one knows that others are hiding on negative channels.  But a hidden
-channel user still cannot be found except by brute-force checking
-through all channels, a hopeless proposition in the face of 10-digit
-channel numbers.  Security through obscurity finally means something.
- 
-** 4.5: Conversations not using channels
- 
-It is possible to conduct conversations with others without using the
-formalized channel structure.  Doing so requires that two people set
-themselves up for private conversation using special commands; see
-User Commands below.
- 
-** 5.2: Screen activity
- 
-Normal messages from other users appear with the originating nickname
-in <angle brackets>.  Private messages arrive with the originating
-nickname in *asterisks*.
- 
-Other output (e.g., /who commands, invitations from other users to
-join channels, and so forth) appears interspersed with other activity
-on the screen.
- 
-* 6: Command structure
- 
-Ordinary text typed at irc is sent as one's messages to everyone else
-on the same channel, modulo personal choices for private messages and
-the like.  Commands to irc itself all begin with a command character,
-which is initially `/' but may be changed to any other character
-desired.
- 
-Commands may in general be abbreviated to a unique prefix.
- 
-** 6.1: Leaving irc
- 
-The way to get out of irc is to enter the /signoff command.  "/si" is
-sufficient.  Also equivalent are "/exit," "/bye," and perhaps "/quit"
- 
-** 6.2: Getting help
- 
-Type "/help."  Follow the instructions.
- 
-** 6.3: User commands
- 
-Other commands supported by irc are:
- 
-      help   signoff       who     whois
-      list     topic      join   channel
-     links       msg    invite    summon
-     users     stats      nick      away
-      info     clear     query
-      date      mode      kick
- 
-*** 6.3.2: signoff
- 
-/signoff exits chat.
- 
-*** 6.3.3: who
- 
-/who returns information on who is using chat.  /who without arguments
-prints info on all users that can be seen.  Users of public channels
-show up with their channel identified.  Users of secret channels
-appear, but they are specified as being on a private, unspecified
-channel.  Users of hidden channels do not appear at all.
- 
-Giving a numeric argument to /who returns only those users of the
-specified channel.  This still doesn't show users of secret or hidden
-channels unless one is actually on that channel.
- 
-*** 6.3.4: whois
- 
-This returns information about individual users.  Say "/whois
-nickname" to get information on the login name and host from which the
-nicknamed user comes.
- 
-*** 6.3.5: topic
- 
-Channels can be given off-the-cuff "topics."  Saying "/topic some
-string of text" will associate that topic with the current channel.
- 
-*** 6.3.6: list
- 
-/list will give lists of active channels, the number of users of each,
-and the topics therewith associated.  Again, secret and hidden
-channels do not appear.
- 
-*** 6.3.7: join & channel
- 
-/join or /channel are the means to enter a channel.  Give a numeric
-argument for the channel one wishes to enter.  If this is a secret or
-hidden channel, /who commands will show oneself and any other users of
-one's channel.
- 
-One's arrival on a channel is announced to the rest of the users
-already on that channel.  Silent, anonymous "lurking" is not
-supported.
- 
-*** 6.3.8: links
- 
-/links lists the currently-active set of chat servers.  Beware: this
-list can be quite long, and will undoubtedly get longer as chat gains
-wider use.  As of 22 March 1989, about 15-20 servers is typical.
- 
-*** 6.3.9: msg
- 
-A single message can be sent privately to a certain user with /msg.
-Type /msg nickname and the text to be sent.  It will be sent privately
-to the indicated nickname.
- 
-*** 6.3.10: invite
- 
-If there is a user online to whom one wishes to speak, one may invite
-that user to join oneself on a certain channel.  One types "/invite
-nickname" with an optional channel number.  The receiving user gets a
-one-line message indicating the sender and the invitation.  The
-receiving user is free to ignore the invitation, of course.
- 
-*** 6.3.11: summon
- 
-An extreme form of /invite is /summon.  "/summon user@host" will
-request the user on the specified host to enter the chat system.  Do
-not do this unless one is fairly sure that one's request will be
-welcome - it can be a fairly disturbing and sometimes irritating
-intrusion.  In order for /summon to work, the specified host must be a
-connected chat server - one can't summon random people from around the
-Internet.
- 
-*** 6.3.12: users
- 
-/users will return a list of the users logged into one's system.  With
-an optional hostname identifying a chat server host, the users logged
-into that system will be listed.
- 
-*** 6.3.13: stats
- 
-This command returns counts of various protocol operations of one's
-chat server.  It is neither particularly useful nor interesting; it
-was, at one time, a debugging aid.
- 
-*** 6.3.14: nick
- 
-One can change nicknames by issuing "/nick new-nickname."  All users
-on one's channel will be advised of the change.  NOTE: If one enters
-chat with a nickname clash (e.g., one's login name is the same as
-someone else's, and the other user got there first), the system will
-not let one enter until one issues a /nick command with a unique
-nickname.
- 
-*** 6.3.15: away
- 
-Sometimes, one wishes to remain connected to the chat system, but one
-must be elsewhere for a while.  One can issue an /away command with
-arbitrary text as argument, which will mark oneself as being away.  If
-someone sends an away'd user a private message (via /msg or in a
-private session set up via /query; see below), the sender will get a
-message back from the server indicating the away-ness and the message
-which was set.
- 
-*** 6.3.16: info
- 
-/info returns information regarding the author and copyright of the
-chat system.
- 
-*** 6.3.17: clear
- 
-At times, one wishes that one's screen weren't so cluttered.  /clear
-makes it so.
- 
-*** 6.3.18: query
- 
-This command is used to set up private communications `outside' the
-normal channel system.
- 
-When one enters "/query nickname," the indicated nickname is set up as
-the sole recipient of anything which one types thereafter.  Thus, if
-user A executes "/query B" and user B executes "/query A," they have
-set up a private communication between themselves.  Significantly, it
-remains possible for them to stay on their respective channels, which
-need not be the same, and listen to whatever conversation is going on
-around them as well, though they cannot respond to that ambient
-conversation without leaving the private conversation they have set up.
- 
-One leaves this private mode by issuing /query without arguments.
- 
-** 6.4: Operator commands
- 
-The chat system administrators on each host have additional
-responsibilities and power over the configuration and operation of the
-servers.  The commands to do so are delineated below.
- 
-*** 6.4.1: oper
- 
-Users who have the potential for operator privileges initially invoke
-those privileges by "/oper nickname password," where nickname is the
-nickname under which operation is intended, and password is the
-password known to the chat system for that nickname.
- 
-*** 6.4.2: kill
- 
-Obnoxious users had best beware the operator who's fast on the /kill
-command.  "/kill nickname" blows any given nickname completely out of
-the chat system.
- 
-Obnoxiousness is not to be tolerated.  But operators do not use /kill
-lightly.
- 
-* 7: Questions, problems, troubles?
- 
-Write mail to local irc coordinator.

month.rxirc

@@ -0,0 +1,6 @@
+expr month word(date(),2)
+if word(date(),1)/=1 then skip 2
+  echo Hey! Today is the 1st of $(month)!
+  skip 1
+    echo Today is just another day of $(month)...
+echo You just ran MONTH RXIRC..  :)

profile.rxirc

@@ -0,0 +1,22 @@
+* Default profile for rxIRC users
+*
+* PF key setup
+pf1 IMM /help
+pf2 IMM /xamin
+pf3 IMM /bye
+pf4 IMM /follow
+pf5 IMM /reply
+pf6 IMM /lastlog
+alias ctoggle %k %c pf$k IMM /toggle $k |join $c|part $c
+ctoggle 9 #talk
+ctoggle 10 #initgame
+
+* Easy use of services
+alias .ni msg nickserv@service.de
+alias .no msg noteserv@service.de
+alias .w .ni whois
+alias .await .no waitfor
+alias .del .no delete
+alias .list .no list
+alias .m .no msg
+alias .read .no read

rxirc.$package

@@ -1,18 +1,21 @@
 *
-* This file contains the definition of the RXIRC package.
+* This file contains the definition of the rxIRC package.
 *
-* Filename Filetype
+* Filename Filetype Filelist
-* -------- --------
+* -------- -------- --------
-  RXIRC    $PACKAGE   recursion!
+  RXIRC    $PACKAGE REXXLIB  recursion!
-  RXIRC    EXEC       the client program
+  RXIRC    README   REXXLIB  introductory information about IRC and rxIRC
-  RXIRC    NAMES      the installation defaults file
+  RXIRC    EXEC     REXXLIB  the client program
-  RXIRC    INSTALL    little installation readme
+  RXIRC    NAMES    REXXLIB  the installation defaults file
-  RXIRC    HELPMENU   the documentation
+  RXIRC    INSTALL  REXXLIB  little installation readme
-  ACTION   HELPIRC    about the set of action commands
+  RXIRC    HELPMENU REXXLIB  the documentation menu
-  CUSTOM   HELPIRC    how to customize
+  ACTION   HELPIRC  REXXLIB  about the set of action commands
-  ETIQ     HELPIRC    irc etiquette (from unix irc distribution)
+  CUSTOM   HELPIRC  REXXLIB  how to customize rxIRC
-  FAQ      HELPIRC    frequently asked questions
+  FAQ      HELPIRC  REXXLIB  frequently asked questions (and answers)
-  MANUAL   HELPIRC    irc manual (from unix irc dist)
+  INTRO    HELPIRC  REXXLIB  IRC introductory manual
-  SPECIAL  HELPIRC    rxIRC specific extra commands
+  SPECIAL  HELPIRC  REXXLIB  rxIRC specific extra commands
-  SYNTAX   HELPIRC    command line usage and options
+  STANDARD HELPIRC  REXXLIB  IRC standard commands
-  SETENV   EXEC       unixlike globalv utility
+  SYNTAX   HELPIRC  REXXLIB  command line usage and options of rxIRC
+  MONTH    RXIRC    REXXLIB  an example of the rxIRC scripting language
+  PROFILE  RXIRC    REXXLIB  rxIRC profiling script to start off with
+  SETENV   EXEC     REXXLIB  unixlike globalv utility

rxirc.helpmenu

@@ -1,20 +1,19 @@
 .cm last change by lynx.
 .mt IRC
  
-                                rxIRC v1.3
+                                  rxIRC
- 
+                                   ^^^
             Internet Relay Chat client program for VM/CMS systems
              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-                     Written by Carl 'lynX' v. Loesch
+                     written by Carl 'LynX' v. Loesch
-                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+                      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-                Move the cursor onto a topic and press ENTER.
+                Move the cursor onto a topic and press ENTER
  
  
-MANUAL                    General Overview about IRC
+INTRO                     Introductory manual for IRC users
-ETIQ                      The IRC Netiquette - How to behave on IRC
+STANDARD                  Standard IRC commands
- 
+SPECIAL                   Special features of rxIRC only
 SYNTAX                    Usage format of rxIRC
-SPECIAL                   Special commands you can only issue from rxIRC
 ACTION                    A set of commands to let you express virtual actions
 CUSTOM                    How to customize your rxIRC
 FAQ                       Frequently asked questions about rxIRC

rxirc.install

@@ -1,21 +1,38 @@
 rxIRC Installation Guide
 ========================
- 
+    
-To run rxIRC you need:
+|  To run rxIRC you need RXSOCKET 2 and REXXWAIT.
-  REXTCPIP which is available from your nearest VM-UTIL - LISTSERV.
+|  You don't need REXTCPIP anymore (Sorry Ken).
-  For example by doing "tell listserv at dearn get rextcpip module".
+    
-  Otherwise you might request it by mail to Ken (KXH105 at PSUVM),
+   Before you start rxIRC you should edit the RXIRC NAMES file which
-  but I'm not sure, if he'd be happy about it.
+   contains all the default values for rxIRC. Most important: the address
- 
+   of your default IRC server host!
-Before you start rxIRC you should:
+    
-  Edit the RXIRC NAMES file which contains all the default values for
+|  On VM/ESA systems you might have to enter the 'NXA' command before
-  rxIRC. Most important: the address of your default server!
+|  starting up rxIRC. I'm not familiar with those systems so I don't know
- 
+|  what needs to be changed to make that work right, same goes for other
-If you have any problems/improvements/suggestions/etc. send mail to me.
+|  exotic VM derivates on which rxIRC makes problems. If you manage to
-Also if you want to be informed of future rxIRC releases, and you do
+|  fix rxIRC up on such systems please send me your changes!
-not read alt.irc or operlist or VM-UTIL or dnet.chat or comp.archives.
+
- 
+|  The VM Gopher client is written to work with the old RXSOCKET version
+|  so you get the problem that either you have Gopher or you have rxIRC
+|  working by default. Sorry but I guess Gopher needs an update!
+
+|  If you have any problems/improvements/suggestions/etc. contact the rxIRC
+|  mailing list rxIRC-l@vmtecqro.qro.itesm.mx.
+
+|  You can subscribe to the mailing list with 'SUB RXIRC-L <fullname>'
+|  sent to listserv@vmtecqro.qro.itesm.mx or LISTSERV AT VMTECQRO.
+
+|  With the AFD and FUI commands you can get automatic information
+|  about new releases of rxIRC from the LISTSERV. You can also decide
+|  to look out for announcements of mine in the VMUTIL-L, alt.irc
+|  or de.comm.internet newsgroups.
+    
+|  However don't expect frequent announcements. Changes to rxIRC
+|  happen seldomly. I usually don't have the time for it.  :(
+
 Ciao  -lynx
-o----------------------------------------------------------------------o
+o-------------------------------------------------------------------o
-| Carlo "Lynx" v. Loesch   is  loesch@informatik.uni-oldenburg.de      |
+| Carl "LynX" v. Loesch   is  loesch@informatik.uni-oldenburg.de    |
-| -----------------------  or  244661 at DOLUNI1.bitnet / .earn        |
+| ----------------------  or  244661 at DOLUNI1.bitnet / .earn      |

rxirc.names

@@ -2,20 +2,34 @@
 * contains installationwide defaults for rxIRC
 :nick.rxIRC
 *
-* insert the network address of a server near to you into here
+* Insert the network address of an IRC server near to you into here..
+* Or activate a temporary choice to be able to contact an IRC
+* operator for help on proper choice of IRC server
+*  (join #Twilight_Zone to meet irc operators)
 *
- :server.arbi.informatik.uni-oldenburg.de
+  :server.irc.uni-erlangen.de
+* :server.irc.mit.edu
+* :server.irc.eunet.fi
+* :server.irc.technion.ac.il
+* :server.irc.virginia.edu
+
+* Some preferences.. You can look into this later on.
+* See also the helpfile about customization.
 *
-* some preferences.. you can look into this later on, see also the helpfile     *
  :logging.off
  :quiet_ignore.off
  :loud_beeps.off
  :show_numbers.off
  :list_all.off
- :beepchar.~
+ :show_time.60
- :hilightchar.%
+ :bold_char.|
+ :beep_char.~
+
+* A command to view files. If there is no BROWSE on your
+* system you can use XEDIT aswell.
 *
-* no change should be necessary here
+ :browser.BROWSE
+
+* No change should be necessary below here
 *
  :port.6667
- :timeout.20

rxirc.readme

@@ -0,0 +1,85 @@
+Subject: rxIRC 2.0 for VM/CMS available
+Newsgroups: bit.listserv.vm-util,alt.irc,de.comm.internet,de.talk.chat
+Keywords: IRC rxIRC rexx vm cms internet bitnet rexx/socket lynx
+
+Introducing rxIRC:
+
+     rxIRC is a client software for VM to connect to the IRC network, the
+Internet Relay Chat, which nowadays counts an average of 1200 users online
+day and night, from all over the world, therefore being the biggest
+international interactive conferencing system on the planet.
+
+     You can make use of this program only if you have access to a machine
+with VM/CMS-type operating system with TCPIP extension installed. To find
+out you logon and type 'CP QUERY TCPIP', if it replies 'TCPIP - DSC' then
+you can make use of this program, otherwise check with your administration.
+
+     rxIRC is a program written in interpreted RexX, a rather easy to learn
+language that gives you a chance to add own features if you miss something
+or modify things you dislike.  rxIRC supports the complete set of standard
+IRC client commands plus a bunch of extras and is more or less up to date
+with the current state of development of the IRC protocol.
+
+New features in rxIRC 2.0:
+
+- now uses RXSOCKET and REXXWAIT
+- has extensive BITNet messaging support
+  (for instance /query +nick queries a bitnet user)
+- /alias with parameter handling
+- variables: /set, /expr (rexx expressions), /echo
+- /if <condition> then <command>
+- /source <scripts>, skip <lines>, stop (sourcing)
+- /pf<n>, /toggle (setup a pf key with alternating commands)
+- /localwho, /catalog
+- /chop, /unchop, /k(ick), /t(opic)
+- /viewlog, /interpret, /applaud
+- documentation has doubled its size..  ;)
+- :show_time, display time every now and then
+- ircII-bold-code displayed with hilighting, :bold_char
+
+Requirements:
+
+     The TCPIP handling of rxIRC is done with help of RXSOCKET version 2.
+You need to have this package installed, or at least the basic modules.
+There are some restrictions concerning the use of RXSOCKET:
+- The new version is not compatible to the old one, if you have
+  programs using version 1 they won't work when you install version 2.
+- VM TCP/IP version 2 is required.
+- rxIRC should run on CMS 3 up to 9 (370, XA, ESA or XC MACHINE modes)
+
+     If you are going to install rxIRC on a big public disk, you probably
+want to install the complete REXX/SOCKET package. You can do so by issueing
+TELL LISTSERV AT CUNYVM GET RXSOCKET PACKAGE. Beware that you will be sent
+the beauty of over 80 files after this!
+
+     If you want to run rxIRC just by yourself, and RXSOCKET isn't available
+already (rxIRC tells you so) then merely issue these commands to get the
+modules:
+   TELL LISTSERV AT CUNYVM GET RXSOCKET MODULE
+   TELL LISTSERV AT CUNYVM GET REXXWAIT MODULE
+
+
+rxIRC 2.0 itself can be obtained from:
+
+<Internet>
+Europe:		ftp nic.funet.fi
+		mget /pub/unix/irc/rxirc/*.*
+
+[Home Site]	ftp ftp.informatik.uni-oldenburg.de  (134.106.1.9)
+		mget /pub/irc/rxirc/*.*
+
+America:	ftp ftp.iastate.edu
+		mget /pub/irc/clients/rxirc/2.0/*.*
+
+		ftp slopoke.mlb.semi.harris.com
+		mget /pub/irc/clients/rxirc/*.*
+
+Australia:	ftp coombs.anu.edu.au
+		mget /pub/irc/rxirc/*.*
+
+<BITnet>
+[Mexico]        TELL LISTSERV AT VMTECQRO GET RXIRC PACKAGE
+
+
+rxIRC installers are invited to join the rxIRC mailing list by sending a
+'SUB RXIRC-L <your-full-name>' command to LISTSERV AT VMTECQRO.

setenv.exec

@@ -1,13 +0,0 @@
-/* SETENV EXEC
- * Set an environment variable for C programs to access
- * last change by Lynx_VM (244661 at DOLUNI1) on Sunday, 12 May 1991
- */
-address 'COMMAND'
-parse arg n c; upper n
-if n="" then
- 'GLOBALV SELECT CENV LIST'
-else if c="" then
- 'GLOBALV SELECT CENV LIST' n
-else
- 'GLOBALV SELECT CENV SET' n c
-exit rc

special.helpirc

@@ -1,50 +1,260 @@
-.cm last change by lynx -- january, 1992
+.cm last change by lynx -- may 93
  
                  _______
-               *|^^^^^^^|*           The Internet Relay Chat program
+               *|^^^^^^^|*           The Internet Relay Chat client
-               *| rxIRC |*            for VM/CMS systems written in
+               *| rxIRC |*        program for VM/CMS systems written
-               *|_______|*            RexX by Carl "lynx" v. Loesch.
+               *|_______|*         in RexX by Carl "LynX" v. Loesch.
                  ^^^^^^^
  
-Special commands of this IRC client program:
+Special features of rxIRC:
+
+Variables:
+| rxIRC has it's own particular implementation of variables. You can
+| set variables with /set or /expr, then use them anywhere within a
+| command line like this:
+|
+|    set c #rxIRC
+|    join $c
+|    expr date date()
+|    echo $(date)
+|    set helpkey 1
+|    pf$(helpkey) immed /help
+|
+| Note how you can use variables even within command names. Variables
+| can be used with or without the braces. However, without braces only
+| the first character is considered part of the name. So 'echo $date'
+| will probably only output 'ate' since '$d' is not defined yet.
+| This is compatible to the way the make program handles variables.
+|
+| With rxIRC variable names are case sensitive!
+|
+| rxIRC provides a set of predefined variables which is compatible
+| to ircII. Here goes a list:
+|   $,   the nickname that last sent you a message, notice or invitation
+|   $:   the nickname that last joined your channel
+|   $A   your current away message
+|   $C   your current channel (or rather 'target' in rxIRC-speak)
+|   $H   last protocol command or numeric received
+|   $I   channel you were invited to last
+|   $K   the command character (usually '/')
+|   $N   your IRC nickname
+|   $Q   current query nickname
+|   $S   current IRC server's name
+|   $T   your query partner, if you are in a query, or otherwise
+|        your target (channel usually)
+|   $V   rxIRC version
+|   $Z   current time
+|   $$   the $ symbol itself
+
+Multiple commands:
+| You can execute multiple commands in a row by putting '::' between them.
+| Like this:
+|    /smile::grin::giggle
+|
+| Notice how the slash is valid for all three of the commands!
+| You need not and may not call something like "/smile::/grin".
+
+Bitnet support:
+| rxIRC now fully supports BITNET messaging, first you have the /tell
+| and /yell commands for traditional way of sending bitnet messages,
+| but you also have /msg +nickname (or /query +nick, /target +nick).
+| When a message target begins with a leading plus sign, rxIRC will
+| not send the message to IRC, but instead send it to the BITNET
+| user specified. So you can easily query a bitnet user with /query +.
+|
+| BITnet message receivers can be specified by nickname from NAMES
+| file or with <userid>@<node> or '<userid> at <node>' or <local_userid>.
+|
+| rxIRC handles incoming BITnet messages properly and will
+| display them as neat as possible. It also checks for /ignore
+| by both nickname and userid@node. If you are /away, also bitnet
+| users are informed of this when they talk to you.
+|
+| rxIRC is capable of sending messages over alternative routes
+| than BITnet allows by default. To achieve this you need to
+| specify "via <node>" at the beginning of a message and all following
+| messages will be forwarded through that node. For instance:
+|
+| /m +strange via psuvm hello!
+|
+| This will send 'hello!' first to PSUVM which then forwards it to MAINE.
+|
+| You can also generate local CP SMSG or CP SEND by specifying "smsg" or
+| "send" as arguments to "via".
+| You can remove a 'via' redirection with "via none".
+| You can set up different via's for each userid@node.
+|
+| To speed up operation, rxIRC keeps internal mappings from nickname to
+| userid@node and from userid@node to nickname. That is, your NAMES file
+| is only queried once. So should you change the userid@node information
+| in your NAMES file from within rxIRC for a nickname that has already
+| been read in, you'll have to restart rxIRC.
+
+Escape characters:
+  There are two escape characters in rxIRC. One is the rxIRC command
+  character, which is by default a slash ('/'). Two is the CMS command
+  escape character '!'. You can abbreviate /exec by just typing !<command>.
+ 
+Default PF keys:
+  rxIRC stores your regular CMS PF-keys setup and re-defines it with
+  leading ! symbols which is the command escape of rxIRC. That means,
+  your normal CMS PF setup works also within rxIRC, unless you redefine
+  keys during your rxIRC session. When leaving, rxIRC puts the PF key
+  settings back as they were before (or almost).
+
+Special commands of rxIRC:
  
 /ABort
    You may leave your session non-caring about the status of your TCPIP
    connection. Use this only when you can't get out with /bye.
  
+/ALias [<alias name> [[<argument catchers>] <command string>]]
+|  You may create your own abbreviations for simple or complex commands.
+|  Commands may not contain the command char. Multiple commands can be
+|  specified by separating them with '::'. User-provided arguments can be put
+|  into variables by writing as many '%<var>' as you need in front of the
+|  command string. Alias names are case insensitive.
+|
+|  Some examples:
+|        alias ni msg nickserv@service.de
+|  This will convince rxIRC to send a message to NickServ with /ni <msg>.
+|
+|        alias date expr date date()::echo $(date)
+|  This makes rxIRC output today's date. Notice how I first used the
+|  /expr command, then the /echo command.
+|
+|        alias ctoggle %k %c pf$k imm /toggle $k |join $c|part $c
+|  This allows you to setup a PF key to join or leave a channel
+|  alternatingly simply by typing "/ctoggle 9 #PartyZone".
+|  Notice how it catches the two arguments and puts it into $k and $c.
+|  Then it calls pf$k which in our case is 'PF9', the rxIRC command
+|  to setup the PF9 key. The key then will immediately perform
+|  "/toggle 9 |join #PartyZone|part #PartyZone" which takes
+|  care of the alternating impact of the pf9 key. See /toggle for details.
+|
+|        alias sgg smile::grin::giggle
+|  /alias is treated differently from all other commands, in the sense
+|  that the line following /alias is not preprocessed as usual.
+|  This means $(variable) is only replaced _when_ the alias is actually
+|  used, not when you define it. Also you can specify multiple commands
+|  within an alias by putting '::' between them. The commands will be
+|  executed in a row as soon as the alias is used.
+|
+|        alias sgg
+|  Using /alias with just one argument will display the definition of
+|  that particular alias.
+|
+|        alias
+|  Using /alias without arguments will list the aliases.
+|
+|  Note: I have not provided a command to un-alias an alias as it's
+|    not really needed.
+ 
+/CAtalog
+|  This command will show you a compact list of all channel names that have at
+|  least 5 persons on them. Unfortunately it takes quite some time to perform
+|  as it has to process a lot of data from the IRC server before being able
+|  to display the collected information.
+
 /Channel <new channel>
    This command will automatically /part you from your previous channel
    before joining this new channel. If you don't want to get confused
    by multiple channels, better always use this command instead of /join.
    Without argument it will tell you what channel you are on.
  
+/CHOP <nickname> [<nickname> [<nickname>]]
+|  Make people channel operators of the current channel.
+|  A shorthand for "/mode $C +o <nickname>"
+
 /CLear
-   Clear the screen.
+   Clear the screen. Just in case you're not used to hitting PA2.
  
 /CMdchar <character>
-   Use an other character than '/' to introduce commands.
+   Use another character than '/' to introduce commands.
  
+/DEscribe <target> <description>
+|  This command generates a CTCP ACTION description like /ME and the
+|  other action commands, but you can specify where to send it to.
+|  Target can be a nickname or a channel, not a bitnet user of course.
+
+/ECHO <text>
+|  Display a line of text to the screen. Typically used combined with
+|  variables like this:
+|    expr t left(time(),5)
+|    echo The time is $t 
+
 /Execute <command>    or more easily just:   !<command>
-   You may execute CMS commands with this, but remember not to stay too
+   You can execute CMS commands with this, but remember not to stay too
-   long outside IRC or the IRC-server might close the connection.
+   long outside IRC or the IRC-server will most likely close your connection.
  
+/EXPRession <varname> <rexx expression>
+|  This allows you to store the value of a rexx expression into a variable.
+|  You can use RexX builtin functions such as substr(), words() giving you
+|  a quite powerful medium to operate on variables.
+|  Some examples:
+|    expr time time()
+|    expr t left('$(time)',5)
+|    echo $t
+|  Notice the trick that makes the contents of $(time) a valid rexx
+|  string by putting '' around it.
+
 /Follow
    If you have just been invited to a channel this is an easier way to
    join it. rxIRC will remember the name of the channel for you.
  
-/IGnore [<nickname> <more nicknames>]
+/IF <rexx condition expression> THEN <command>
+|  This will make rxIRC perform <command> only when <condition> is met.
+|  The <condition> must not contain spaces, in exchange it may contain
+|  RexX builtin function.. you can even make floating point calculus! 
+|  Here goes an example:
+|    expr a 5/2
+|    if 2*$a=5 then echo People really win on IRC!
+
+/IGnore <nickname>|<address-mask> [<more arguments>]
    If you don't want to receive a person's messages, you can use /ignore
    on him. Use it again to remove the /ignore. Without arguments you
-   get the list of people being ignored by you. The ignore function
+|  get the list of people being ignored by you. The ignore function
-   captures both /msg's and /notice's from the specified person. It
+|  catches /msg's, /notice's and bitnet messages from the specified
-   sends a notice back to the sender telling him that you are not
+   nickname. It also sends a notice back to the sender telling him that
-   receiving his messages unless you specify it to be silent with
+   you are not receiving his messages unless you specify it to be silent with
-   the startup option "(Quiet".
+|  the rxIRC option "(Quiet". An <address-mask> is a string that will
+|  match a set of hosts from whom you don't want to hear anything.
+|  For example "*.ais.org" will keep any message from a user of that
+|  organization away from you. You can apply this to BITnet nodes aswell.
  
+/INTerpret <rexx statement>
+|  This will simply execute a RexX statement.  A command for hackers.
+
+/Invite <nickname> [<channel>]
+|  I made the channel argument optional. "/i lynx" will invite me to
+|  your current channel without hassle.
+
+/K <nickname>
+|  The quick way to kick somebody off a channel. This is a shorthand
+|  for /kick $C <nickname>
+
+/LAstlog [<number of lines>]
+   This shows you the last messages you received, usually 12 lines, but
+   you can request more (up to 50) or less.
+ 
+/LIst
+   Shows a list of channel names, number of users and topic.
+|  There must be at least 8 people on the channel for it to be listed,
+   unless you are running in LIST_ALL mode (See options in SYNTAX).
+
+/Localwho     (you may as well type /LCL)
+|  Shows you a list of IRC users that are from the same site as you or
+|  are using an IRC server which runs at your institution.
+
 /LOgging [ON | OFF]
    You can switch the logging on and off. That means you get a transcription
    of your IRC session into the file IRC LOG A0 on disk.
  
+/NAmes
+|  Shows a list of channels and people on them, but only those channels
+|  that have at least 7 visible persons aboard. This should be modified into
+|  something more flexible but for now it's like this. See also: /cat
+
 /Query [ <nickname> | <channel> ]
    You can get into a dialogue mode with a person, all lines you type are
    sent as private message to this person. If you want to talk onto a
@@ -52,25 +262,71 @@ Special commands of this IRC client program:
    leaving the /query. To leave the /query use /query without arguments.
    If you want to use #-type channels you need to /query those, too.
  
+/PF<n> <mode> <string>
+|  You can use /pf1 through /pf24 to setup your PF keys. This command is
+|  actually nothing but a short form of !cp set pf<n> <mode> <string>
+|  so better refer to the CP SET manual for details on usage.
+|  Ok, I will resume: <mode> can either be IMMediate or DELayed.
+
 /Reply
    This is a shortcut to get into a /query with the person that last sent
-   you a message.
+   you a message, notice or invitation.
  
 /Request <nickname> | <channel>
    Send a CTCP (Client To Client Protocol) Version Request to a person
    or a whole Channel. IRC program that have this implemented will
    automatically respond as does rxIRC when it gets such a request.
  
+/SAY <words>
+|  Speaks to the channel. Useful for aliases and source-scripts.
+
 /SErver <address> [ <port> [ <timeout> ] ]
    Switch to another IRC server. rxIRC will exit if the server does not
    respond.
  
+/SET [<variable> [<value>]]
+|  Set or query the contents of a variable, or if used without arguments,
+|  give a listing of all user-defined variables.
+
+/SKIP <number_of_lines>
+|  Tell rxIRC to skip the next <number> of lines of the file being
+|  sourced. Meaningless to be entered interactively. Lookup up /source
+|  for a practical example of skip's use.
+
+/SOurce <filename>
+|  Looks for a file called '<filename> RXIRC *' on all linked disks,
+|  then attempts to read it and execute it line by line.
+|  /source profile is automatically executed when you start up rxIRC.
+|  Lines are always treated as commands. The commands may not have the
+|  leading command character (the slash). Multiple commands can be specified
+|  in one line separated by '::' and lines can be indented.
+|  Especially interesting for scripts are the commands /if, /skip, /stop.
+|  For instance like this:
+|
+|    expr month word(date(),2)
+|    if word(date(),1)/=1 then skip 2
+|      echo Hey! Today is the 1st of $(month)!
+|      skip 1
+|        echo Today is just another day of $(month)...
+|    echo Anyway.. what I really wanted to say...
+|
+|  This shows how to make an if-then-else construct in an rxIRC script
+|  in a pretty assembler-like manner..      ;)
+|  Indenting improves readability slightly.
+
 /STatus
    This outputs some of rxIRC's variables, tells you what channel you are
    talking to (Target), what query, where you got invited to last and who
    last sent a message to you.
    It also shows a /whois of yourself.
  
+/STOP
+|  This command only makes sense within scripts. It stops rxIRC from
+|  executing scripts any longer. Might be useful combined with /if.
+
+/T <topic>
+|  Set a topic on the current channel. Shorthand for "/topic $C <topic>".
+
 /TAlkto <new target>
    This is the ONLY command to allow you to switch to another channel when
    you are on multiple channels! You can NOT use /join for that.
@@ -81,15 +337,64 @@ Special commands of this IRC client program:
    command.
  
 /TCPipstatus
-   Gives a brief not very useful information about your TCPIP status.
+|  Gives some information about your connection to IRC. The number of bytes
+|  in the input buffer might be interesting. If there are any, then your
+|  connection to the server is probably suffering from netlag. 
  
-/WHO
+/TEll <nickname>|<user@node>|<user at node> [via <gateway>] message
-   The /who command can now be used without arguements, if you are talking
+|  Use this command to send a message to a user in BITNet.
-   to a channel, it will show you the WHO list of that channel.
+|  See note about the bitnet support of rxIRC at the top of this file.
+ 
+/TOGgle <key> <c><first command><c><second command>
+|  This is a tricky feature to allow you to program pf keys with alternating
+|  function each time you use them. <key> is the number of the pf key.
+|  <c> is the character used to separate the commands. I use '|' usually.
+|  Toggle performs <first command>, then sets up PF<key> to call the
+|  inverted command '/TOGGLE <key> <c><second command><c><first command>'
+|  Here's one practical example you can include in your PROFILE RXIRC:
+|
+|    pf5 imm toggle 5 |query Nickserv@service.de|query
+|
+|  This will set up the PF05 key to /query or un-/query NickServ.
+|  Look also for the 'ctoggle' alias described in /alias.
+
+/Umode <mode switches>
+|  Change your "mode", that is change some flags in the IRC server
+|  concerning your connection. See IRC documentation about this.
+|  This is just a shorthand for "/mode <yournick> <switches>".
+
+/UNCHOP <nickname> [<nickname> [<nickname>]]
+|  Remove channel operatorship of the current channel from some people.
+|  A shorthand for "/mode $C -o <nickname>"
+
+/VIewlog
+|  A handy command to check out today's IRC log.
+|  Uses the CMS command 'BROWSE'. Hope that one exists on every CMS.
+
+/WHO [<channel> | <nickname> | <matchstring>]
+|  The /who command can now be used without arguments, if you are talking
+|  to a channel, it will show you the WHO list of that channel.
+   You can match hosts as well as real names with <matchstring>, so
+   the normal way to get a list of e.g. all italians is to type '/who *.it'.
+|  The logic that displays WHO output has become very complex (and
+|  colourful if you have colours by the way). It will display the channel
+|  information only if it still fits into the line. Also, if there is still
+|  not enough space, it will truncate the hostname and put an '*' after the
+|  '@' to indicate that. But it will only truncate the hostname to a certain
+|  minimum, from then on it will shorten the real name information and
+|  indicate that with a pair of periods, but that only happens in extreme
+|  cases. /who should always give you as much info as possible without
+|  wrapping lines. If you however do need more info don't forget about /whois.
  
 /Xamine
    Quicky to get a /whois of the person that lest sent you a message.
  
-/* <remark> [ */ ]
+/Yell <arguments>
-   With this you can add RexX-style comments in your IRC PROFILE.
+|  This is just like /tell with one little difference. Yell prepends
-   Lines beginning with /* are skipped.
+|  your own nickname in front of the message. Use it when it's likely
+|  that your dialogue partner is not running a message handling program
+|  and doesn't know your userid by heart.
+
+* <remark>
+|  With this you can add CMS-style comments in your RXIRC source files.
+|  Lines beginning with * are skipped.

standard.helpirc

@@ -0,0 +1,390 @@
+ 
+ 
+                      STANDARD IRC COMMANDS
+ 
+ 
+Author:  Robert D. Blais
+Email:  <IO00058@Maine.maine.edu>
+        <IO00058@Maine.Bitnet>
+Revised:  11 November 1992
+Version:  1.10
+ 
+PURPOSE:  This document attempts to explain, in simple terms, the
+standard Internet Relay Chat (IRC) commands that all IRC client
+programs should support.  It is intended to supply information
+for new users not familiar with IRC and to serve as a reference
+for experienced users.
+     Since there are many different programs on several different
+operating systems, client-specific information has been left out.
+Users should refer to the documentation that came with their IRC
+program to see what internal commands it supports and what, if
+any, variations on the standard commands that client might have.
+ 
+NOTATION:  The "standard" command character for IRC clients is
+the virgule (/) and has been used exclusively in this document.
+However, most IRC client programs allow the user to change the
+command character to something else.  If yours is different,
+substitute your command character wherever you see a virgule.
+     Many of the commands accept arguments and many of the
+arguments will vary, depending on exactly what you are doing.
+Variable arguments have been listed within angle brackets.  If
+there are more than one possible type of argument, the choices
+are separated by a pipe (|).  For example, <nickname|channel>
+indicates that the argument can either be a user's nickname or a
+channel name.
+     Commands marked with an asterisk (*) are propagated across
+the entire network and should be used sparingly to save bandwidth
+and avoid confusion.
+     The term "wildcards" is used frequently in this document.
+Whenever a command allows wildcards, it means that certain parts
+of the command, such as "user" in user@host, can be replaced by
+an asterisk (*) and the command will effect the first or possibly
+all occurrences that match.  As a rule, if you don't know exactly
+what effect wildcards will have, don't use them.
+ 
+CREDITS:  The information contained in this document has been
+culled several sources, including the alt.irc group in Usenet
+news, the helpserver IRCIIHelp, and from the  author's own
+experience using IRC and studying and experimenting with the
+code for some of the client programs.  Special thanks to Carl
+"LynX" von Loesch for his help and suggestions.
+ 
+AWAY: *
+     Occasionally you may be away from your terminal for several
+     minutes but want to remain connected to IRC.  The away
+     command allows you to specify a message stating that you are
+     away and, optionally, should tell people when you'll be
+     back.  Other users will see the message whenever they send
+     you a private message or run the whois command on your
+     nickname.
+ 
+     Syntax:  /away <message>
+              /away
+ 
+     <message> is the new message you specify.
+     To remove an away message, issue the command with no
+     argument.
+ 
+ADMIN:
+     The admin command gives the name and email address of the
+     person in charge of the IRC server you or another user is
+     using.
+ 
+     Syntax:  /admin <nickname>
+              /admin
+ 
+     <nickname> is the nickname of the person who's server you
+     want administration information from.  If you omit the
+     nickname you'll get information about your own server.
+ 
+CHANNEL: *
+     The channel command is used to change channels.  On some
+     clients it will part you from the last channel you joined,
+     but on others it doesn't.
+ 
+     Syntax:  /channel <channel>
+ 
+     <channel> is the name of the new channel you wish to join.
+ 
+INFO:
+     The info command gives information about the server
+     software.
+ 
+     Syntax:  /info
+ 
+INVITE:
+     Occasionally you may want to invite another user to your
+     channel.  The easiest way to do so is with the invite
+     command.  It is also the only way for other users to join a
+     channel if the channel mode +i is in effect on that channel.
+ 
+     Syntax: /invite <nickname> <channel>
+ 
+     <nickname> is the nickname of the person you are inviting
+     and <channel> is the channel you are inviting them to.
+ 
+JOIN: *
+     Use the join command to join or create a channel.  If the
+     channel is public or you have been invited to it, you'll
+     join it.  If not, you get a message saying that you cannot
+     join the channel.
+ 
+     Syntax:  /join <channel>
+ 
+     <channel> is the channel you wish to join.
+ 
+KICK: *
+     The kick command is used by ChanOps to remove an offending
+     user from a channel.
+ 
+     Syntax:  /kick <channel> <nickname>
+ 
+     <channel> is the channel the offending user is to be removed
+     from and <nickname> is that user's nickname.
+ 
+LIST:
+     Use the list command to get a list of active channels.  This
+     list will show the channel names, number of users on the
+     channel, and the channel topic, if there is one.  If a
+     channel has mode +s in effect, it's name will not be shown
+     but the number of users and the channel topic will still be
+     displayed.
+ 
+     Syntax:  /list
+ 
+LINKS:
+     The links command lists the IRC servers currently connected
+     to an IRC server.
+ 
+     Syntax:  /links <server>
+              /links
+ 
+     <server> is the server whose links you're interested in.  If
+     you omit the server, you'll see the links to your own
+     server.  Wildcards may be used in server names.
+ 
+LUSERS:
+     The lusers command shows how many people are currently on
+     IRC.  It is automatically called when you sign onto IRC.
+ 
+     Syntax:  /lusers
+ 
+MODE: *
+     There are two types of mode commands.  Channel mode commands
+     effect a channel and user mode commands effect only you,
+     the user.  Any user can set user modes at any time, but
+     you must be a ChanOp to set channel modes.  Several modes
+     can be set at once.  (+ or - before the <mode> turns modes
+     on or off, respectively)
+ 
+  User modes:
+ 
+     Syntax:  /mode <nickname> <mode>
+ 
+     <nickname> is your nickname and the possible modes are:
+      Mode    Description
+       i    - Sets you invisible so you don't show up in /who.
+       w    - Allows you to see Wallops (messages to IRCOps.)
+       s    - Allows you to see server messages and /kills.
+       o    - (Available only to IRCOps.)
+ 
+     Note:  some clients have a /umode command for setting
+            user modes.
+ 
+  Channel modes:
+ 
+     Syntax:  /mode <channel> <mode> <arguments>
+ 
+     <channel> is the channel you wish to set the mode on and
+     available modes and their arguments are shown below.
+ 
+     Mode Arguments   Description
+       b <nick>    - Ban <nick> from a channel.  <nick> may be a
+                     nickname or a nick!user@host name.
+                     Wildcards are allowed if the user@host form
+                     is used.
+       i           - Makes channel invite-only.
+       l <number>  - Limits the number of users on a channel.
+                     <number> is the maximum number of users
+                     allowed.
+       m           - Channel is moderated, so only channel
+                     operators can talk.
+       n           - No MSGs to the channel are allowed from
+                     people not on the channel.
+       p           - Channel is private and people on it won't
+                     show up in /who, /names, or /whois.  It will
+                     show up in /list.
+       s           - Channel is secret, so the channel name won't
+                     show up in /list.
+       t           - Topic limit; only the channel operators may
+                     change the topic.
+       o <nick>    - Makes <nick> a channel operator.
+ 
+MOTD:
+     The MOTD (Message Of The Day) command redisplays the MOTD
+     that you saw when you signed on to the server or the new one
+     if it has been changed since you signed on.  It can also be
+     used to show the MOTD on another server.
+ 
+     Syntax:  /motd <nickname|server>
+              /motd
+     <nickname|server> is the nickname of another user or a
+     server.  If wildcards are used in the server name, the MOTD
+     of the first server to match the mask will be shown.
+ 
+MSG:
+     Use the msg command to send a private message to another
+     user or to a channel.  If you send a private message to a
+     single user, only that user will see it (hopefully, but IRC
+     is not very secure so use caution.)  If you send it to a
+     channel, all the users on that channel will see it.
+ 
+     Syntax:  /msg <nickname|channel> <message>
+ 
+     <nickname|channel> is the person or channel you are sending
+     the message to and <message> is the message you want to
+     send.
+ 
+NAMES:
+     The names command lists the nicknames of all the users
+     on a channel or all of the users on IRC (unless they have
+     set usermode +i).
+ 
+     Syntax:  /names <channel>
+ 
+     <channel> is the channel you want to list the users on.  If
+     <channel> is omitted, you will see a list of nicknames for
+     EVERY channel on IRC!
+ 
+NICK: *
+     Use the nick command to change your nickname.
+ 
+     Syntax:  /nick <nickname>
+ 
+     <nickname> is the new nickname you want.
+ 
+NOTICE:
+     The notice command is generally not necessary, but if you
+     have an important message that you want everyone on the
+     channel to pay attention to, you might find it useful.  It
+     is also a requirement that all automatic replies, such as
+     ctcp replies, robot and server replies, etc., be in the form
+     of a notice.
+ 
+     Syntax:  /notice <nickname|channel> <message>
+ 
+     <nickname|channel> is the person or channel you are sending
+     to and <message> is the message you want people to see.
+ 
+PART: *
+     Use the part command to leave a channel.
+ 
+     Syntax:  /part <channel>
+ 
+     <channel> is the channel you wish to leave.
+ 
+QUERY:
+     Use the query command to start a private conversation with
+     another user or to converse with a particular channel when
+     you're on multiple channels.  While in a query, all messages
+     you type *without* using the / or /msg  commands, will
+     only be seen by the person or channel you are in the query
+     with.
+ 
+     Syntax:  /query <nickname|channel>
+              /query
+ 
+     <nickname|channel> is the person or channel you wish to
+     start a query with.  To end a query and resume talking to
+     your channel, issue the command with no argument.
+ 
+QUIT: *
+     Use the quit command to end your IRC session.
+ 
+     Syntax:  /quit <reason>
+ 
+     <reason> is optional.  If you want to let people know why
+     you're quitting, you can give a brief reason.
+ 
+TIME:
+     The time command shows the current time at a server.
+ 
+     Syntax:  /time <nickname|server>
+              /time
+ 
+     If <nickname|server> is specified, the time at that server
+     will be displayed.  If no argument is given, it will return
+     the time at your server.  Wildcards may be used in the
+     server name.
+ 
+TOPIC: *
+     Use the topic command to set a topic line for your channel.
+     The topic line will be displayed in the channel list.
+ 
+     Syntax:  /topic <channel> <topic>
+ 
+     <channel> is the channel you're setting the topic for and
+     <topic> is the topic message.
+ 
+TRACE:
+     The trace command displays a list of the server links that
+     are connected to a particular server.
+ 
+     Syntax:  /trace <server>
+              /trace
+ 
+     <server> is the server whose links you want to see.  If you
+     omit the server, the links to your server will be shown.
+ 
+VERSION:
+     The version command will show what version of IRC a server
+     is running.  It can also be used to find out what client
+     program another user is using.
+ 
+     Syntax:  /version <nickname|server>
+              /version
+ 
+     If a nickname is specified, it will return the client
+     version of that user's program.  If a server is specified,
+     it will return the version of IRC running on that server.
+     If you omit the arguments it will return the version of the
+     server you are using.
+ 
+WHO:
+     Use the who command to get a list of users on a channel, at
+     a particular host, or with a common text string in their
+     name.
+ 
+     Syntax:  /who <text|channel|server>
+ 
+     <text|channel|server> can be text in a user's nickname,
+     hostname or IRCname, a channel name, or a server name.
+     Wildcards are allowed.
+ 
+WHOIS:
+     Use the whois command to get specific information about an
+     IRC user.
+ 
+     Syntax:  /whois <server> <nickname>
+              /whois <nickname>
+ 
+     <server> is the server the user specified in <nickname> is
+     on.  <server> may be omitted.
+ 
+WHOWAS:
+     Use the whowas command to get information about a user who
+     recently left IRC.
+ 
+     Syntax:  /whowas <nickname>
+ 
+     <nickname> is the nickname of the person you want
+     information about.
+ 
+/:
+     The virgule (/) is used to talk to the current channel when
+     you are in a query with another user or channel.  The
+     current channel is normally the last channel you joined,
+     however, some clients allow you to specify which channel is
+     current when you are on multiple channels.
+ 
+     Syntax:  / <message>
+ 
+     <message> is the message to be sent to the current channel.
+ 
+     In addition to the above commands, there are several other
+commands that are primarily for the use of IRCOps.  Some of the
+commands shown below provide some humorous replies when issued by
+regular users, proving that IRC coders have a sense of humor.
+Other commands give information which is fairly meaningless to
+the average user but hard-core users may be interested.  Try them
+at your own risk. :-)
+ 
+CONNECT, DEOP, DIE, HASH, KILL, OPER, PASS, REHASH, RESTART,
+SQUIT, STATS.
+ 
+--
+NOTE:  This document is hereby placed in the public domain.  If
+you copy it, please attribute the source.  If you modify it,
+please note who you are, what changes you made and the date of
+those changes in the document header.  Take the credit you
+deserve, but give credit where it is due.  Thanks.

syntax.helpirc

@@ -14,14 +14,12 @@ Usage from CMS:
 Options:
  
   Port <port-number>   IRC usually runs on port 6667, here you might
-		       set another.. but you might not find a server
+                       set another.. but you might not find a server
-		       on an other port...
+                       on an other port...
   LIst_all {ON | OFF}  Show also channels without topic with /list.
   Logging {ON | OFF}   You may start the logging from the command line.
   LOUd {ON | OFF}      This defines if an external 'BEEP' module should
-		       be called whenever you receive an IRC beep.
+                       be called whenever you receive an IRC beep.
   Numbers {ON | OFF}   Shows the numbers of IRC server replies.
   Quiet {ON | OFF}     If you want to use the quiet ignoring.
-  Timeout <seconds>    The time to wait before giving up trying to connect
-		       the server.