github.com/GeorgeMcMullen.rxIRC
1
0
Fork 0
mirror of https://github.com/GeorgeMcMullen/rxIRC.git synced 2026-02-10 02:10:44 +00:00
Code Issues Releases Wiki Activity

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

Browse Source
This commit is contained in:
George McMullen
2013-06-08 14:40:36 -07:00
parent 578e8e6d54
commit 1631cab07b
10 changed files with 1221 additions and 401 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
action.helpirc
View File

@@ -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

56
custom.helpirc
View File

@@ -10,16 +10,19 @@
*** How to customize rxIRC ***
The IRC PROFILE startup file:
This file should contain a series of lines that are executed by
rxIRC as if you would type them in as soon as you get connected to
a server. You could for instance do "/join #fun" or "/who bunny"
The PROFILE RXIRC startup file:
| This file should contain a series of lines that are /source'd by
| rxIRC as soon as you get connected to the first server. You could
| 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:
Some defaults for the rxIRC program are defined here:
server: the Internet address of an irc server
port: the TCP/IP port it runs on, usually 6667
timeout: when rxIRC should give up on connections
logging: make it ON or OFF
quiet_ignore: usually OFF
loud_beeps: ON only when a BEEP MODULE is available.
show_numbers: ON shows the reply numbers of server replies, for freaks.
list_all: show also channels without topic in /list, i use OFF.
beep_char: the character that gets translated into a beep and back.
highlight_char: the char that gets translated into an inverse on ircII.
The RXIRC PFKEYS file is obsolete. You can use the 'PF' commands
| from PROFILE RXIRC now.
Defaults in the RXIRC NAMES file (the rxIRC configuration file):
server: The internet address of an IRC server
port: The TCP/IP port it runs on, usually 6667
| browser: Name of a command good for showing files.
| Typically BROWSE, but if that's not there try XEDIT.
| timeout: Not used anymore, you can remove it
logging: Set it to ON or OFF for default logging
quiet_ignore: Usually OFF
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.

70
faq.helpirc
View File

@@ -1,28 +1,32 @@
Frequently asked questions:
--------------------------
1. Why can't rxIRC have /alias and /on and /notify and everything else
that ircII has?
What am I supposed to write into the :server field in RXIRC NAMES?
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
of time to develop and most of all consume to much speed. And they
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?
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
I get a lot of error messages.
When I use one of the new action commands on a channel, like /smile
I get error messages.
The CTCP ACTION protocol is still rather new, not everyone likes, not
everyone supports it, and most of all, a lot of people do not have up
to date IRC programs. When you get such error messages better not use
the commands on those channels. On other channels you might find people,
who have newer clients, and you'll be able to communicate with the new
commands.
| There are controverse notions of the ethics of the CTCP ACTION protocol.
| I think it's a valid alternative form of communication and should be
| supported, but since I invented it I might be biased. Well some IRC
| client programmers insist on not supporting this protocol and return
| all sorts of funny messages. Eventually avoid using these 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
'loesch@informatik.uni-oldenburg.de' (internet).
Write mail to 'loesch@informatik.uni-oldenburg.de' (internet).
or to '244661 at DOLUNI1' (bitnet)

35
rxirc.$package
View File

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

1000
rxirc.exec
View File

File diff suppressed because it is too large Load Diff

17
rxirc.helpmenu
View File

@@ -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
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Move the cursor onto a topic and press ENTER.
written by Carl 'LynX' v. Loesch
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Move the cursor onto a topic and press ENTER
MANUAL General Overview about IRC
ETIQ The IRC Netiquette - How to behave on IRC
INTRO Introductory manual for IRC users
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

53
rxirc.install
View File

@@ -1,21 +1,38 @@
rxIRC Installation Guide
========================
To run rxIRC you need:
REXTCPIP which is available from your nearest VM-UTIL - LISTSERV.
For example by doing "tell listserv at dearn get rextcpip module".
Otherwise you might request it by mail to Ken (KXH105 at PSUVM),
but I'm not sure, if he'd be happy about it.
Before you start rxIRC you should:
Edit the RXIRC NAMES file which contains all the default values for
rxIRC. Most important: the address of your default server!
If you have any problems/improvements/suggestions/etc. send mail to me.
Also if you want to be informed of future rxIRC releases, and you do
not read alt.irc or operlist or VM-UTIL or dnet.chat or comp.archives.
| To run rxIRC you need RXSOCKET 2 and REXXWAIT.
| You don't need REXTCPIP anymore (Sorry Ken).
Before you start rxIRC you should edit the RXIRC NAMES file which
contains all the default values for rxIRC. Most important: the address
of your default IRC server host!
| On VM/ESA systems you might have to enter the 'NXA' command before
| 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
| exotic VM derivates on which rxIRC makes problems. If you manage to
| fix rxIRC up on such systems please send me your changes!
| 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
| Carlo "Lynx" v. Loesch is loesch@informatik.uni-oldenburg.de |
| ----------------------- or 244661 at DOLUNI1.bitnet / .earn |
o-------------------------------------------------------------------o
| Carl "LynX" v. Loesch is loesch@informatik.uni-oldenburg.de |
| ---------------------- or 244661 at DOLUNI1.bitnet / .earn |

28
rxirc.names
View File

@@ -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.~
:hilightchar.%
:show_time.60
: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

351
special.helpirc
View File

@@ -1,50 +1,260 @@
.cm last change by lynx -- january, 1992
.cm last change by lynx -- may 93
_______
*|^^^^^^^|* The Internet Relay Chat program
*| rxIRC |* for VM/CMS systems written in
*|_______|* RexX by Carl "lynx" v. Loesch.
*|^^^^^^^|* The Internet Relay Chat client
*| rxIRC |* program for VM/CMS systems written
*|_______|* 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
long outside IRC or the IRC-server might close the connection.
You can execute CMS commands with this, but remember not to stay too
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
captures both /msg's and /notice's from the specified person. It
sends a notice back to the sender telling him that you are not
receiving his messages unless you specify it to be silent with
the startup option "(Quiet".
| get the list of people being ignored by you. The ignore function
| catches /msg's, /notice's and bitnet messages from the specified
nickname. It also sends a notice back to the sender telling him that
you are not receiving his messages unless you specify it to be silent with
| 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
The /who command can now be used without arguements, if you are talking
to a channel, it will show you the WHO list of that channel.
/TEll <nickname>|<user@node>|<user at node> [via <gateway>] message
| Use this command to send a message to a user in BITNet.
| 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> [ */ ]
With this you can add RexX-style comments in your IRC PROFILE.
Lines beginning with /* are skipped.
/Yell <arguments>
| This is just like /tell with one little difference. Yell prepends
| 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.

8
syntax.helpirc
View File

@@ -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
on an other port...
set another.. but you might not find a server
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.