I can partially answer my questions. Removing also Seen does away with the ByteString.index error. Must check the code to see why. Two more concrete questions a) how do I gracefully leave lambdabot? ctrl-C or killing it from another shell are the only ways out I found so far. b) what does lambdabot expect in the fptools directory? Cheers, Daniel Am Freitag, 22. Juni 2007 20:10 schrieb ich:
Greetings, lambdabot segfaulted when installing Fact Haddock Quote Source Todo Where
What's special about them? I.e., why did they cause a segfault and the others not?
And, how could I build a lambdabot _with_ them (though I'm not sure, I'll actually want them, but I might).
Without these, I now have an apparently working lambdabot, well, not properly working. First time I started it, all seemed well, but from then on: $ ./lambdabot Initialising plugins ..................................sending message to bogus server: IrcMessage {msgServer = "freenode", msgLBName = "urk!<outputmessage>", msgPrefix = "", msgCommand = "NAMES", msgParams = [""]} ............... done. Main: caught (and ignoring) IRCRaised Data.ByteString.index: index too large: 0, length = 0 lambdabot> > 3+7 Main: caught (and ignoring) IRCRaised Data.ByteString.index: index too large: 0, length = 0 10 lambdabot>
The bogus message thing also appeared the first time, I hope this is meant to be so. But what about the ByteString.index exception? Where might that come from? How to get rid of it?
Finally, is there a tutorial/manual for using lambdabot?
Thanks for any help, Daniel