Skip to content
Just what the world needs: another IRC bot
Racket Shell
Pull request Compare This branch is 22 commits ahead, 90 commits behind offby1:master.
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.
bugs
.gitignore
.mailmap
AUTHORS
GNUmakefile
README
README.bowdlerize
README.irc-servers
TODO
analyze-quotes.rkt
backfill.rkt
clearenv.rkt
corpus.rkt
el-buggo
elis-log-parsing-ideas.rkt
eval-trouble
freenode-main.rkt
get-big-log.sh
git-version.rkt
http.rkt
incubot-tests.rkt.inc
incubot.rkt
info.rkt
irc-process-line.rkt
iserver.rkt
lexer.rkt
line-structure
loop.rkt
memory-notes.org
quotes
quotes.rkt
re.rkt
regenerate-log-word-map.rkt
reloadable.rkt
sandboxes.rkt
servers.rkt
sighting-test.rkt
sketch.rkt
spelled-out-time.rkt
timer.rkt
tinyurl.rkt
update-sightings.rkt
userinfo.rkt
utils.rkt
utterance.rkt
vars.rkt
xlate.rkt
zdate.rkt

README

Start the bot via "./freenode-main.rkt" at the shell.  I think doing
"racket freenode-main.rkt" will fail mysteriously.

Getting an error about "rackunit" not being available?  That can be
caused by using the "racket-textual" package instead of "racket".

specs etc:
http://tools.ietf.org/html/rfc1459
http://www.irchelp.org/irchelp/rfc/ctcpspec.html

Run the tests like this:

    $ raco test -x .

Unfortunately, you'll have to pay attention to the output of "raco
test", since it will likely exit with 0 status even if some of the
tests fail.  This is IMHO a misfeature of "raco test"; the Racket
developers seem disinclined to change it (see
http://bugs.racket-lang.org/query/?cmd=view&pr=13573).
Something went wrong with that request. Please try again.