From 98c0512eec526f9c21fe9575f9a77de83ae70c8e Mon Sep 17 00:00:00 2001 From: Jeremy Fincher Date: Fri, 27 Aug 2004 05:35:50 +0000 Subject: [PATCH] Updated, thanks again Grantbow. --- docs/GETTING_STARTED | 35 ++++++++++++++++++----------------- 1 file changed, 18 insertions(+), 17 deletions(-) diff --git a/docs/GETTING_STARTED b/docs/GETTING_STARTED index f0af8c9e5..8eeba66e6 100644 --- a/docs/GETTING_STARTED +++ b/docs/GETTING_STARTED @@ -107,24 +107,25 @@ Supybot wants to send a message that's longer than that. What it does, then, is break it into "chunks" and send the first one, following it with "(X more messages)" where X is how many more chunks there are. To get to these chunks, use the more command. One way to -try is to look at the listing of configuration groups for the bot -(more on this in the CONFIGURATION document) by giving the command -"config list supybot". Last I checked, it'll overflow into a second -chunk. When you invoke this command, you should see output like: +try is to look at the default value of +supybot.replies.genericNoCapability -- it's so long that it'll +stretch across two messages. - nick, ident, user, server, password, channels, prefixChars, - defaultCapabilities, defaultAllow, defaultIgnore, - humanTimestampFormat, externalIP, bracketSyntax, pipeSyntax, - followIdentificationThroughNickChanges, alwaysJoinOnInvite, - showSimpleSyntax, maxHistoryLength, nickmods, throttleTime, - snarfThrottle, threadAllCommands, pingServer, pingInterval, - upkeepInterval, flush, (1 more message) - -Now, to see the rest of the output, simply give the command "more", -and it will show you the rest: - - more - httpPeekSize, and defaultSocketTimeout + $config default + supybot.replies.genericNoCapability + jemfinch|lambda: You're missing some capability + you need. This could be because you actually + possess the anti-capability for the capability + that's required of you, or because the channel + provides that anti-capability by default, or + because the global capabilities include that + anti-capability. Or, it could be because the + channel or the global defaultAllow is set to + False, meaning (1 more message) + $more + jemfinch|lambda: that no commands are allowed + unless explicitly in your capabilities. Either + way, you can't do what you want to do. You should now have a solid foundation for using Supybot. Be sure to check the help that is built-in to the bot itself if you have any