00:09 <rikai> Igneous: hah, i was actually thinking of doing something quite similar to that myself... :)

00:12 <rikai> My only real critique would be perhaps to use "#{@match[:nick]} meant: #{@match[:msg]}" instead of "#{@match[:nick]}: #{@match[:msg]}" :)

00:14 <Igneous> good idea

00:15 <Igneous> so now, it should wrok like that

00:15 <Igneous> s/ro/or/

00:15 <EatFoot> Igneous meant, "so now, it should work like that"

00:16 <Igneous> I've also got a grep function, for going back through $log

00:17 <Igneous> .grep function

00:17 <EatFoot> (19:16:57 - 05/13/2013) Igneous: I've also got a grep function, for going back through $log

00:18 <Igneous> It's a testiment to both the simplicity of ruby and cinch, that I can implement a full (to-memory) channel logger in like, three lines of code

00:30 <rikai> Mmm, i think you can save a few characters sticking with the other output syntax. The : instead of the , i mean that way you dont need the quotes. Gives a whole two more characters for displaying the message. :P

00:30 <rikai> And agreed.

00:31 <rikai> Your bot source available somewhere? :)

00:31 <Igneous> probably tomorrow, I'm a little ashamed of it right now

00:32 <Igneous> it'll be up at http://github.com/igneous

00:32 <rikai> Hah. Dont be, can almost guarantee your code is better than mine. :P

00:34 <rikai> for example, my messy modifications of mutewinter's showbot to add in i18n...: https://github.com/mutewinter/Showbot/pull/55/files

00:34 <rikai> :P

00:34 <EatFoot> ^ Mass-restructuring of bot configuration. by rikai · Pull Request #55 · mutewinter/Showbot · GitHub

00:34 <rikai> Ha! Thats another thing i was thinking about adding xD

00:38 <Igneous> oh and here's another thing that is so stupid and yet so useful

00:38 <Igneous> .eval Array.methods.first 10

00:41 <EatFoot> [:[], :try_convert, :allocate, :new, :superclass, :json_creatable?, :freeze, :===, :==, :<=>]

00:42 <Igneous> IRC repl!

02:43 <rikai> nice nice

03:13 <catepillar> how secure is the .eval?

06:38 <zewelor> how can i make bot to keep his nickname after server timeouts and reconnect ? It gets nick with _ on the end as previous session still hangs on the server. Is there some option to set for bot to try to regain his original nickname ?

07:51 <sleetdrop> zewelor: I use a loop to wrap up the start / stop of a bot https://gist.github.com/sleetdrop/5574355

07:56 <zewelor> what exception is generated when bot reconnects ?

08:03 <sleetdrop> zewelor: I don't know

08:28 <zewelor> i dont think it generates any, so i need some other solution

08:28 <zewelor> i was thinking about some timer plugin to check if the original nick is available yet

08:55 <waxjar> you can add a handler for nick changes/quits: if the person with nickname you want changes theirs or if that person quits, change your own to that one

08:55 <waxjar> ^ zewelor

09:08 <sleetdrop> zewelor: My bot is simple, it just send svn commit notifications, so if somethings unexpected happens, just restart it will be okay. The idea of use a timer plugin to check for the nick will be okay.

09:08 <sleetdrop> zewelor: And if there is a nickserv, why not just register the nick, and auth the nick everytime reconnect

09:15 <zewelor> sleetdrop: Nickserv isn't on every network, and if it is when old session still doesnt time out, I don't think new session can auth with that nickname ?

09:16 <zewelor> waxjar: that could probably work, i will look into it