SLirc - IRC for customization junkies.

Hiya. If your out to customize, read README.gutsbonesbloodtoilsweat, and
remember that I'd be very happy if you'd send me any files you create or
change. Catch me online and DCC it to me, or email it to
<slirc@non.entity.org>

If you're not yet compiled, though, you might try make. Some people have
reported success with this method.  But only if they've already installed
libslang.so.1.3.* as their global libslang.

If you haven't unpacked the archive yet, then you're completely stuffed,
because it's obvious that you can't be helped, since you're not reading this
file.

Now...

INSTALLATION

(0) This depends on libslang, version 1.3.7 or later. 
    After making slang you can either install slang as usual, OR, you can
    copy slang/src/slang.h to slirc's 'include' dir, and copy
    slang/src/objs/libslang.so.1.3.8 to slirc's 'lib' dir...
		you'll also need the symlink lib/libslang.so in there,
		so...   
		       cd lib; ln -sf libslang.so.1.3.8 libslang.so

    In the latter case, you will be building an slirc which is dynamically
    linked against the new libslang, (if you want to keep the old
    libslang-??? as your default installation for now).

    (
     dwd-note: It's possible to have both live, which I do.
     Installing the new slang manually over an RPM installed 0.x.y
     leaves Jed and such all woking fine.
    )

(1) Look over the Makefile, if you like.
    (a) If you plan to install slirc globally (eg under  /usr/local/*), just do
		    make
    (b) If you only want to run slirc from the build directory, do
		    make CFG_DIR=$PWD
				(or whatever the equivalent is in your shell).
		
(2) edit scripts/config.sl changing whatsoever thou pleasest.
    You'll probably at least want to change the servers lines.
    Same goes, actually, for any other *.sl scripts you fancy changing
    for yourself only. Like, don't inflict bot scripts on everyone... :-)

(3) OPTIONALLY,
    make tests, if you want to play with the simple *.sl scripts
    in the tests subdir.  These are stand-alone progs for playing
    with (or testing) some of the general-purpose intrinsics provided
    by the vfile-module and utils-module.
    See the README in that subdir if you're interested.

(4) run the thing from the build directory by:
       ./slirc
    or
       LD_PRELOAD=lib/libslang.so ./slirc
    the latter in the case that you don't have a global libslang.so.1.3.8.
		In that case you might want to do something like
       alias slirc='LD_PRELOAD=lib/libslang.so ./slirc'


You still here? Oh. Hmm. Instructions, huh?

INSTRUCTIONS

Type. Scroll up and down with the six keys arranged (on PC) as
         <insert>    <home>    <page-up>
         <delete>    <end>    <page-down>
(insert scrolls up 1 line, and delete scrolls down 1 line, the others
are as labelled.)

Try /help to get a pitifully cryptic command-summary.

Use left/right arrows and backspace to edit your command-line.

Use the up/down arrows to scroll through history of previous commands.

Join channels. That kind of stuff.

Cool features which I personally like include the ability to scroll back
through the entire session, flip between channels and people with the F keys,
and generally do funky stuff.

DCC:

The DCC stuff is probably less than standard. It's worth noting that there
are DCC docs included (SJB: not really). These are crap. Mainly not due to
the people who wrote them, but due to DCC itself being appallingly designed,
IMHO.

SLirc doesn't autoget DCC files sent to it. It tells you when someone
tries to send, and you have to "/dcc get theirnick" to accept the send.
It'll kill off DCC transfers it considers unsafe: it ignores any host
information sent to it, and refuses to connect to ports lower than 1024.
It will honour any REJECT sent to it, but it checks that they're legit first.

Any DCC sends by you will be host authenticated, but there's no ident
support yet - it's debatable how useful this is anyway. If a host connects
from a different machine than the one the user you're sending to, then the
DCC session is dropped.

DCC chat is available, now, but Stan needs to write documentation for it
here...

[SJB: heh!]

Messages:

Messages from unknown users are ignored, but you're warned about them, so
you can just do a /whois on the user, then ask them what they said, if you
like. You can, of course, change this... It's yet to upset me.

BUG REPORTING

If you find a bug, just let me know. If you can fix it, then great. If you
can't, then just tell me as much as you can. Email to slirc@non.entity.org

dwd : Dave Cridland : dwd@non.entity.org

SLirc stuff to slirc@non.entity.org please...

[23-08-99: I (SJB) think non.entity.org is defunct.. try instead... ]
[SJB: Stan Brooks : stabro@megsinet.net ]