17:56 <leftylink> dominikh: hmm, you said groups have plugin scope, what do you mean by that? If you mean in PluginOne I have a matcher in group_a, and in PluginTwo I have a matcher in group_a, and you expect them not to be in the same group... my current experience is that they do in fact end up in the same group

17:58 <dominikh> if PluginOne has a group_a and PluginTwo has a group_a, those will be two different group_a's and both handlers can execute for the same message

18:06 <leftylink> hmm, ok so here is groupbot http://lpaste.net/109819

18:06 <leftylink> check out #cinch-bots

18:11 <dominikh> cool, that's broken then

18:12 <dominikh> will have to work around it, I guess

18:13 <dominikh> right now, group names are globally scoped.

18:18 <dominikh> maybe one day I'll write Cinch 3 after all…

19:12 <sarkyniin> hey, how hard would it be to write a "!recap" function in cinch?

19:13 <sarkyniin> basically, a function that displays the 20 lines of text/joins before you joined

19:13 <dominikh> relatively easy; the only thing to look out for is to order the messages correctly

19:14 <sarkyniin> is there some kind of logging function in cinch?

19:14 <dominikh> you'd simple write handlers for the events you want to log (channel messages, joins, parts, quits), record them in an appropriate data structure, and provide a handler for !recap to send the user the contents of that data structure.

19:15 <dominikh> *simply

19:15 <sarkyniin> oh, so it's pretty easy

19:16 <dominikh> I could probably write it in ~10 minutes, so yeah, rather easy.

19:20 <sarkyniin> dominikh: should I use the Logger cinch class for this?

19:20 <dominikh> no.

19:20 <dominikh> you should be writing normal plugins

21:08 <onewheelskyward> You might look at this for ideas. https://github.com/Quintus/cinch-plugins/blob/master/plugins/history.rb

21:17 <sarkyniin> yeah onewheelskyward

21:17 <sarkyniin> I saw that afterwards