[00:02:00] -supybot- Strike|work has quit oftc (Quit: leaving)
[00:15:57] *** jetscreamer has joined #supybot
[01:28:02] *** agile has quit IRC
[01:47:23] <indro> hi
[01:47:39] <indro> anyone know why my supbot dont display special character like ä ü ö?
[01:47:50] <indro> *supybot
[02:09:50] *** TFKyle has quit IRC
[02:12:48] *** TFKyle has joined #supybot
[02:16:57] *** TFKyle has quit IRC
[02:21:27] *** TFKyle has joined #supybot
[03:03:44] <indro> hi TFKyle
[03:07:22] <TFKyle> hi
[03:24:23] *** agile has joined #supybot
[03:51:55] *** TFKyle has quit IRC
[03:52:10] *** TFKyle has joined #supybot
[04:52:04] *** factor has left #supybot
[05:08:35] *** jetscreamer has quit IRC
[05:10:05] *** jetscreamer has joined #supybot
[05:44:35] *** jetscreamer has quit IRC
[06:10:44] *** zann has quit IRC
[06:14:13] *** zann has joined #supybot
[06:24:41] <Hagabard> indro: it doesn't handle unicode properly yet
[06:46:49] -supybot- Strike|laptop has joined on oftc
[06:52:17] *** zanny has joined #supybot
[06:57:51] *** evan_d has joined #supybot
[06:58:59] <evan_d> Is there any way to check for syntatical errors in a plugin without trying to load it in an instance of supybot?
[07:00:04] *** beoba has quit IRC
[07:06:14] <Synapse> evan_d: I'm sure you could run it through python somehow.
[07:07:47] <evan_d> when I try that it just calls the Supybot shutdown operation.
[07:09:22] <supybot> <Strike|laptop> Syntax errors in a plugin shouldn't shut down supybot
[07:13:01] <evan_d> sorry to paste flood, but I just want to clarify:
[07:13:04] <evan_d> supybot@pclug:~$ python plugins/EnemyTerritory.py
[07:13:05] <evan_d> INFO 2006-02-08T01:07:01 Shutdown initiated.
[07:13:05] <evan_d> INFO 2006-02-08T01:07:01 Killing Driver objects.
[07:13:05] <evan_d> INFO 2006-02-08T01:07:01 Killing Irc objects.
[07:13:07] <evan_d> INFO 2006-02-08T01:07:01 Shutdown complete.
[07:13:10] <evan_d> supybot@pclug:~$ supybot --version
[07:13:10] <evan_d> supybot 0.80.1
[07:13:25] <Hagabard> upgrade! ;)
[07:13:40] <evan_d> heh, planning on it
[07:13:42] <Hagabard> that's oooold :)
[07:14:06] <supybot> <Strike|laptop> well yeah, upgrade, but also, why are you running the plugin from the command line?
[07:14:25] <supybot> <Strike|laptop> load the plugin via the "load" command on the bot while it's running
[07:14:28] <Hagabard> and if you are running a script that old you might want to look at my old qstat script. :)
[07:14:43] <evan_d> Strike|laptop: I'm trying to find a way to test it for errors without loading the plugin within an instance of supybot.
[07:14:52] <evan_d> the plugin, that is
[07:15:10] <supybot> <Strike|laptop> open a python interpreter and import it
[07:15:20] <supybot> <Strike|laptop> or better yet
[07:15:26] <supybot> <Strike|laptop> upgrade and use the testing framework
[07:15:38] <supybot> <Strike|laptop> (which you get for free with the new improved supybot plugins)
[07:15:41] <evan_d> testing framework? are there docs somewhere?
[07:15:42] <evan_d> ooo
[07:15:59] <evan_d> will do, thanks Strike
[07:16:10] <supybot> <Strike|laptop> no problem, and yes there are
[07:16:13] <supybot> <Strike|laptop> I'm getting a link for you
[07:16:48] <supybot> <Strike|laptop> plugin author tutorial for new plugins:  http://supybot.com/documentation/help/tutorial/plugin-author-tutorial
[07:16:51] <supybot> <supybot> Title: Writing Your First Supybot Plugin Supybot Website (at supybot.com)
[07:16:57] <evan_d> awesome, thanks!
[07:16:59] <supybot> <Strike|laptop> advanced testing stuff not covered in that tutorial:  http://supybot.com/documentation/help/tutorial/advanced-plugin-testing
[07:17:02] <supybot> <supybot> Title: Advanced Plugin Testing Supybot Website (at supybot.com)
[07:36:36] -supybot- Strike|laptop has quit oftc (Quit: Leaving)
[08:53:50] *** Crazysim has quit IRC
[09:00:21] *** mazon is now known as Mazon
[09:38:09] *** zanny has left #supybot
[10:20:40] *** Freso has joined #Supybot
[10:33:10] *** dfletcher|Zzz has joined #supybot
[10:33:21] <dfletcher|Zzz> hi
[10:33:22] <dfletcher|Zzz> ok bye
[10:33:23] <dfletcher|Zzz> :P
[10:33:26] *** dfletcher|Zzz has left #supybot
[12:05:17] *** brad2901 has quit IRC
[13:44:16] *** jetscreamer has joined #supybot
[14:42:39] *** Crazysim has joined #supybot
[15:29:43] -supybot- Strike|work has joined on oftc
[15:29:47] -supybot- mode change by ChanServ on oftc: +o Strike|work
[15:57:11] *** dju` has joined #supybot
[16:39:54] *** dju` has quit IRC
[16:48:48] *** Mazon is now known as mazon
[17:16:01] *** mazon is now known as Mazon
[17:56:53] *** dju` has joined #supybot
[20:29:47] *** Sedated has quit IRC
[21:05:32] *** beoba has joined #supybot
[21:11:13] *** Sedated has joined #supybot
[21:47:04] *** dju` has quit IRC
[23:06:27] *** josef has joined #supybot
[23:07:08] <josef> is there a way to make supybot recognize commands without the @ or whatever you have configured?
[23:23:41] <Freso> josef: You can always just address the bot.
[23:23:45] <Freso> supybot: Right?
[23:23:55] <Freso> supybot: help
[23:23:57] <supybot> <Strike|work> Freso: /topic  :)
[23:24:16] <Freso> Heh. Right. :p
[23:24:22] <supybot> <Strike|work> (he doesn't reply when addressed by nick because it gets annoying when talking about supybot the program and supybot the bot answers)
[23:24:24] <josef> Freso: yeah but i have a specific need for it to monitor for specific commands without it being addressed
[23:24:27] <Freso> Oh well, it's possible in a standard install. =)
[23:24:56] <Freso> Strike: Yeah. I can follow that reasoning.
[23:25:08] <supybot> <Strike|work> josef: I think there might be a way of doing that, but I personally think it's a bad idea
[23:25:30] <josef> i konw its a bad idea, but until i can obsolete this other bot i need that functionality
[23:25:43] <supybot> <Strike|work> is the other bot an infobot or something?
[23:26:17] <josef> we use another bot here that handles stuff for us, and i'm tying to obsolete it, but first i have to mimick its capabilities
[23:26:23] <josef> its kibot
[23:27:21] <supybot> <Strike|work> what better time to transition to new ways of doing things than with a new bot? :)
[23:27:36] <josef> preaching to the choir
[23:27:50] <supybot> <Strike|work> I mean, if they don't want to do it now, why would they want to do it later?
[23:28:19] <josef> we have to keep the functionality of the older bot in place, which only does it that particular way
[23:28:36] <josef> like, its still going to be doing its job, but my bot is going to be doing the same job, only better
[23:28:56] <josef> so instead of having people do two different commands, i'll just pick up on the command that gets run for the existing bot
[23:29:12] <supybot> <Strike|work> have you poked around the config options, I think there's something like what you want
[23:29:29] <josef> i was looking around but i couldnt find anything that matches
[23:29:48] <josef> i could set the address strings, but then it wouldnt recognize it as an actual command
[23:29:57] <supybot> <Strike|work> yeah
[23:30:08] <supybot> <Strike|work> @config search address
[23:30:09] <supybot> <supybot> Strike|work: supybot.reply.whenNotAddressed, supybot.reply.whenAddressedBy, supybot.reply.whenAddressedBy.chars, supybot.reply.whenAddressedBy.strings, supybot.reply.whenAddressedBy.nick, supybot.reply.whenAddressedBy.nick.atEnd, supybot.reply.whenAddressedBy.nicks, supybot.plugins.Infobot.unaddressed, supybot.plugins.Infobot.unaddressed.snarfDefinitions, (1 more message)
[23:30:17] <supybot> <Strike|work> @config help supybot.reply.whenNotAddressed
[23:30:18] <supybot> <supybot> Strike|work: Determines whether the bot should attempt to reply to all messages even if they don't address it (either via its nick or a prefix character). If you set this to True, you almost certainly want to set supybot.reply.whenNotCommand to False.  (Current value: False)
[23:30:30] <supybot> <Strike|work> kaching
[23:31:24] <josef> wonderful, thanks much Strike|work
[23:31:31] <supybot> <Strike|work> no problem
[23:33:18] <josef> oops
[23:33:23] <josef> then it complained about everything
[23:33:32] <josef> i guess some tweaking is in order
[23:34:06] <supybot> <Strike|work> set supybot.reply.whenNotCommand to False
[23:34:11] <supybot> <Strike|work> (like the config help above says)
[23:35:24] <josef> oh derr
[23:35:27] <josef> thx
[23:35:37] <supybot> <Strike|work> no problem :)
[23:42:18] <josef> can i add supybot.reply.whenNotAddressed to the channels.conf and have it only set for specific channels?
[23:45:05] <supybot> <Strike|work> @config list supybot.reply
[23:45:06] <supybot> <supybot> Strike|work: #inPrivate, #requireChannelCommandsToBeSentInChannel, #showSimpleSyntax, #whenNotAddressed, #whenNotCommand, #withNickPrefix, #withNotice, @#mores, @error, @format, @whenAddressedBy, maximumLength, oneToOne, and withNoticeWhenPrivate
[23:45:17] <supybot> <Strike|work> see the # in front of "whenNotAddressed"?
[23:45:23] <supybot> <Strike|work> that means you can do channel-specific config
[23:45:42] <supybot> <Strike|work> configuration
[23:45:44] <supybot> <Strike|work> er
[23:45:45] <supybot> <Strike|work> http://supybot.com/documentation/help/tutorial/configuration
[23:45:48] <supybot> <supybot> Title: Configuring Supybot Supybot Website (at supybot.com)
[23:47:31] <josef> heh where does it store its information i'm having problems finding it.  it baned me b/c of invalid command flooding :)
[23:49:00] <supybot> <Strike|work> in the conf file you specify when you start the bot
[23:49:13] <supybot> <Strike|work> but you should do as much as possible through the bot itself
[23:49:16] <supybot> <Strike|work> it's just easier
[23:50:43] <josef> @config list supybot.abuse.flood.command
[23:50:45] <supybot> josef: @invalid, maximum, and punishment
[23:51:13] <josef> @config list supybot.abuse.flood
[23:51:14] <supybot> josef: @command and @ctcp

top