mirror of
https://github.com/GeorgeMcMullen/rxIRC.git
synced 2026-01-27 04:33:01 +00:00
Compare commits
5 Commits
2.0.1
...
developmen
| Author | SHA1 | Date | |
|---|---|---|---|
|
2a8bb81121 | ||
|
|
34051b49ad | ||
|
|
75c03e2bdc | ||
|
|
e341a3219c | ||
|
|
8801ea2c49 |
7
00readme
7
00readme
@@ -1,7 +0,0 @@
|
||||
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.
|
||||
@@ -25,10 +25,5 @@ ACTION commands:
|
||||
with the /ME or /Emote commands, like this:
|
||||
/me feels a little hungry now.
|
||||
|
||||
You can also try to add your own commands into the program. With the way
|
||||
it is done, it should be easy to understand also for someone who doesn't
|
||||
really know REXX. Just edit the RXIRC EXEC, move to the bottom of the file,
|
||||
and turn a page back. You'll see where you can add your lines.
|
||||
|
||||
Good suggestions for action commands are always welcome, send them to me
|
||||
by NoteServ or mail. :)
|
||||
And finally create your own commands with help of the /ALIAS command.
|
||||
See the "SPECIAL" help page.
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
.cm last change by lynx -- april 25, 1991
|
||||
.cm last change by lynx -- nov 94
|
||||
|
||||
_______
|
||||
*|^^^^^^^|* The Internet Relay Chat program
|
||||
@@ -11,19 +11,26 @@
|
||||
|
||||
|
||||
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).
|
||||
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 USERINFO requests are sent
|
||||
to you while you are ircing with rxIRC.
|
||||
unless otherwise specified in the command line. First it looks for
|
||||
:ircnick and :ircname tags in your 'self-entry' in your namesfile,
|
||||
if not present it will take the normal :nick and :name entries.
|
||||
Environment settings supercede these entries. You may also set a
|
||||
'motto' line by adding a :motto tag, which will be displayed when
|
||||
USERINFO requests are sent to you while you are on IRC. Particularely
|
||||
| interesting is how you can specify a :wwwport entry, which will acti-
|
||||
| vate rxIRC's builtin httpd (world wide web server). :wwwport should
|
||||
| contain a number greater than 1023. Also look up the /export command
|
||||
| to see how to use the httpd. Use a WWW client to learn about writing
|
||||
| HTML files. That is beyond the scope of these help files.
|
||||
|
||||
Environment settings:
|
||||
You may use 'setenv' or 'globalv' to put some values into environment
|
||||
@@ -32,29 +39,30 @@ Environment settings:
|
||||
other IRC programs.
|
||||
|
||||
The RXIRC PFKEYS file is obsolete. You can use the 'PF' commands
|
||||
| from PROFILE RXIRC now.
|
||||
from PROFILE RXIRC now.
|
||||
|
||||
Defaults in the RXIRC NAMES file (the rxIRC configuration file):
|
||||
server: The internet address of an IRC server
|
||||
| pass: A password, if your IRC server needs it (rarely ever)
|
||||
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
|
||||
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).
|
||||
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.
|
||||
|
||||
52
faq.helpirc
52
faq.helpirc
@@ -2,28 +2,19 @@ Frequently asked questions:
|
||||
--------------------------
|
||||
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!
|
||||
| You don't have a server? Check out the "servers.*" list which
|
||||
| is available by ftp on cs-ftp.bu.edu in /irc/support/.
|
||||
|
||||
|Why can't rxIRC have /on and /notify and everything else
|
||||
|that ircII has?
|
||||
Why can't rxIRC have everything 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! :)
|
||||
|
||||
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
|
||||
|
||||
Why when I do something outside of rxIRC with /exec, or simply read
|
||||
the /help files, the server signs me off?
|
||||
@@ -40,24 +31,17 @@ You have a bug, "/who -h *.il" doesn't work!
|
||||
to ircII. They are NOT standard. It is the normal and natural way
|
||||
to do it simply with "/who *.il". Or what about trying /local.
|
||||
|
||||
When I use one of the new action commands on a channel, like /smile
|
||||
I get error messages.
|
||||
|
||||
| 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.
|
||||
|
||||
|
||||
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.
|
||||
|
||||
It tells me loader table overflow
|
||||
|
||||
Use 'SET LDRTBLS 10' in your PROFILE or in the RXIRC EXEC.
|
||||
|
||||
You still have a question?
|
||||
Write mail to 'loesch@informatik.uni-oldenburg.de' (internet).
|
||||
or to '244661 at DOLUNI1' (bitnet)
|
||||
Write mail to <lynx@imp.de> or to '244661 at DOLUNI1'.
|
||||
|
||||
@@ -10,13 +10,8 @@ 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
|
||||
pf11 DEL /notify
|
||||
|
||||
* here comes the list of friends to notify for
|
||||
* these are just examples, fill in your own
|
||||
notify SymLynX Lambretta
|
||||
|
||||
677
rxirc.exec
677
rxirc.exec
File diff suppressed because it is too large
Load Diff
@@ -1,12 +1,11 @@
|
||||
.cm last change by lynx.
|
||||
.mt IRC
|
||||
|
||||
rxIRC
|
||||
^^^
|
||||
Internet Relay Chat client program for VM/CMS systems
|
||||
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
||||
written by Carl 'LynX' v. Loesch
|
||||
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
||||
by Carl v. Loesch
|
||||
^^^^^^^^^^^^^^^
|
||||
Move the cursor onto a topic and press ENTER
|
||||
|
||||
|
||||
|
||||
@@ -1,38 +1,45 @@
|
||||
rxIRC Installation Guide
|
||||
========================
|
||||
|
||||
| To run rxIRC you need RXSOCKET 2 and REXXWAIT.
|
||||
| You don't need REXTCPIP anymore (Sorry Ken).
|
||||
|
||||
|
||||
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
|
||||
| Carl "LynX" v. Loesch is loesch@informatik.uni-oldenburg.de |
|
||||
| ---------------------- or 244661 at DOLUNI1.bitnet / .earn |
|
||||
|
||||
On VM/ESA systems you can try to obtain the ESA-Version of RXSOCKET,
|
||||
or switch into the 370 mode (with SET MACHINE 370 and IPL CMS).
|
||||
If you're lucky it will work from scratch even on those systems,
|
||||
it's a question of how your mainframe is being configured.
|
||||
|
||||
When it tells you the TCPIP DATA file is missing, you probably
|
||||
need to ACCESS (or even CP LINK) the appropriate system disk,
|
||||
which is tipically labeled ('TCPIP'). Try 'QUERY DASD'.
|
||||
|
||||
When you see the whole internet address in people's messages
|
||||
instead of just the nickname, or other similar weird things
|
||||
you might have some improper ASCII/EBCDIC translation set up!
|
||||
In that case check that STANDARD TCPXLATE and STANDARD TCPXLBIN
|
||||
from your TCPIP system disk come before other * TCPXLATE files.
|
||||
|
||||
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. :(
|
||||
|
||||
--
|
||||
____ http://www.noris.de/~lynx/
|
||||
LynX Carl von Loesch lynx@imp.de
|
||||
|
||||
~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~
|
||||
LynX@You.might.aswell.use.This.as.my.Email.Address.Biol.Chemie.TU-Muenchen.DE
|
||||
|
||||
16
rxirc.names
16
rxirc.names
@@ -1,18 +1,26 @@
|
||||
* RXIRC NAMES
|
||||
* contains installationwide defaults for rxIRC
|
||||
* do NOT change the next line
|
||||
:nick.rxIRC
|
||||
*
|
||||
* 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)
|
||||
* A list of servers exists in ftp://cs-ftp.bu.edu/irc/support/
|
||||
*
|
||||
:server.irc.uni-erlangen.de
|
||||
:server.irc.informatik.uni-oldenburg.de
|
||||
* :server.irc.fu-berlin.de
|
||||
* :server.irc.mit.edu
|
||||
* :server.irc.eunet.fi
|
||||
* :server.irc.technion.ac.il
|
||||
* :server.irc.virginia.edu
|
||||
|
||||
|
||||
* In case your default server requires a client password, you can enter it
|
||||
* here. However this is a pretty unusual case.
|
||||
*
|
||||
* :pass.PassWord
|
||||
|
||||
* Some preferences.. You can look into this later on.
|
||||
* See also the helpfile about customization.
|
||||
*
|
||||
@@ -24,12 +32,12 @@
|
||||
: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.
|
||||
*
|
||||
:browser.BROWSE
|
||||
|
||||
|
||||
* No change should be necessary below here
|
||||
*
|
||||
:port.6667
|
||||
|
||||
84
rxirc.readme
84
rxirc.readme
@@ -1,44 +1,37 @@
|
||||
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
|
||||
|
||||
Subject: rxIRC 4.1 - IRC client for VM/CMS 370 systems
|
||||
Newsgroups: bit.listserv.vm-util,alt.irc.announce,de.comm.internet,de.talk.chat
|
||||
Keywords: IRC rxIRC rexx vm cms internet bitnet rexx/socket
|
||||
|
||||
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
|
||||
Internet Relay Chat, which nowadays counts an average of 3000 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.
|
||||
|
||||
chances are good, otherwise check up 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
|
||||
|
||||
|
||||
New features in rxIRC 2.1:
|
||||
|
||||
* /notify - Finally it's in, thanks to Michael Letourneau
|
||||
* builtin WWW server, secure and stable!
|
||||
* /export to specify what files are available for WWW, typically /export *.html
|
||||
* /omit - Filter channel talk that you don't want to listen to
|
||||
* Support for server passwords
|
||||
* The CONNECT RXIRC script is sourced right after you connect to a server
|
||||
* Small fixes and protocol parsing updates
|
||||
|
||||
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:
|
||||
@@ -46,40 +39,35 @@ There are some restrictions concerning the use of RXSOCKET:
|
||||
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:
|
||||
|
||||
|
||||
|
||||
rxIRC itself can be obtained from:
|
||||
|
||||
<Internet>
|
||||
Europe: ftp nic.funet.fi
|
||||
Europe:
|
||||
[Home Site] ftp ftp.m.biologie.tu-muenchen.de (129.187.220.2 or .9)
|
||||
mget /pub/comp/rxirc/*.*
|
||||
|
||||
[Finland] 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.
|
||||
|
||||
13
setenv.exec
Normal file
13
setenv.exec
Normal file
@@ -0,0 +1,13 @@
|
||||
/* 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 SETL' n c
|
||||
exit rc
|
||||
550
special.helpirc
550
special.helpirc
@@ -1,4 +1,4 @@
|
||||
.cm last change by lynx -- may 93
|
||||
.cm last change by lynx -- nov 94
|
||||
|
||||
_______
|
||||
*|^^^^^^^|* The Internet Relay Chat client
|
||||
@@ -7,89 +7,90 @@
|
||||
^^^^^^^
|
||||
|
||||
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
|
||||
|
||||
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)
|
||||
| $U URL of your builtin httpd, if active
|
||||
$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".
|
||||
|
||||
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.
|
||||
|
||||
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, but only once.
|
||||
|
||||
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
|
||||
@@ -101,7 +102,7 @@ Default PF keys:
|
||||
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
|
||||
@@ -109,53 +110,53 @@ Special commands of rxIRC:
|
||||
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.
|
||||
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.
|
||||
|
||||
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
|
||||
@@ -163,9 +164,9 @@ Special commands of rxIRC:
|
||||
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>"
|
||||
|
||||
Make people channel operators of the current channel.
|
||||
A shorthand for "/mode $C +o <nickname>"
|
||||
|
||||
/CLear
|
||||
Clear the screen. Just in case you're not used to hitting PA2.
|
||||
|
||||
@@ -173,88 +174,108 @@ Special commands of rxIRC:
|
||||
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.
|
||||
|
||||
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
|
||||
|
||||
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 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.
|
||||
|
||||
/EXPOrt <filemasks>
|
||||
| With this command you define which files can be accessed via WWW if you
|
||||
| activate the builtin httpd, using a <filename>.<filetype> notation as is
|
||||
| visible from WWW (hello.html being the file HELLO HTML *). Typical usage
|
||||
| is "/export *.html", remember that index.html is the file that is loaded
|
||||
| first when a user inspects your WWW server.
|
||||
|
||||
/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.
|
||||
|
||||
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.
|
||||
|
||||
/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>]
|
||||
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...> ]
|
||||
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
|
||||
| catches /msg's, /notice's and bitnet messages from the specified
|
||||
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.
|
||||
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.
|
||||
|
||||
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.
|
||||
|
||||
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>
|
||||
|
||||
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,
|
||||
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.
|
||||
|
||||
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
|
||||
|
||||
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
|
||||
|
||||
/NF [ <nicknames> ]
|
||||
| Short form of /notify
|
||||
|
||||
/NOTIFy [ <nicknames> ]
|
||||
| With this command you can tell rxIRC to watch out for certain people to
|
||||
| show up on IRC. You will be informed within one minute when they sign on.
|
||||
| Using /notify on the nickname again will remove it from the list.
|
||||
|
||||
/OMit [ <nickname>|<address-mask> ] [ <more...> ]
|
||||
| This one lets you filter the communication on a channel by leaving the
|
||||
| lines out that were typed by people you aren't listening to anyway.
|
||||
| So it's much like an /ignore for channel talk.
|
||||
|
||||
/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
|
||||
@@ -263,11 +284,11 @@ Special commands of rxIRC:
|
||||
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.
|
||||
|
||||
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, notice or invitation.
|
||||
@@ -278,42 +299,43 @@ Special commands of rxIRC:
|
||||
automatically respond as does rxIRC when it gets such a request.
|
||||
|
||||
/SAY <words>
|
||||
| Speaks to the channel. Useful for aliases and source-scripts.
|
||||
|
||||
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.
|
||||
|
||||
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.
|
||||
|
||||
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.
|
||||
|
||||
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,
|
||||
| /source CONNECT right after you have connected to the server.
|
||||
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
|
||||
@@ -321,12 +343,12 @@ Special commands of rxIRC:
|
||||
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.
|
||||
|
||||
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>".
|
||||
|
||||
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.
|
||||
@@ -337,64 +359,64 @@ Special commands of rxIRC:
|
||||
command.
|
||||
|
||||
/TCPipstatus
|
||||
| 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.
|
||||
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.
|
||||
|
||||
/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.
|
||||
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.
|
||||
|
||||
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>".
|
||||
|
||||
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>"
|
||||
|
||||
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.
|
||||
|
||||
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.
|
||||
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.
|
||||
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.
|
||||
|
||||
/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.
|
||||
|
||||
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.
|
||||
With this you can add CMS-style comments in your RXIRC source files.
|
||||
Lines beginning with * are skipped.
|
||||
|
||||
Reference in New Issue
Block a user