dominikh changed the topic of #cinch to: The IRC Framework | Latest version: Cinch 2.0.5
jonahR has joined #cinch
jonahR has quit [Client Quit]
ColdBlooder has joined #cinch
nickrw has quit [Ping timeout: 264 seconds]
nickrw has joined #cinch
Spami has joined #cinch
tempestas has quit [Remote host closed the connection]
tempestas has joined #cinch
Fatguy has joined #cinch
ColdBlooder has quit [Remote host closed the connection]
v0n has joined #cinch
Fatguy has quit [Read error: Connection reset by peer]
Fatguy has joined #cinch
Fatguy has quit [Client Quit]
ColdBlooder has joined #cinch
bhaak has quit [Ping timeout: 256 seconds]
bhaak has joined #cinch
ColdBlooder has quit [Read error: Connection reset by peer]
ColdBlooder has joined #cinch
sleetdrop has joined #cinch
Spami has quit [Quit: Leaving]
Spami has joined #cinch
sleetdrop has quit [Quit: Computer has gone to sleep.]
Spami has quit [Quit: This computer has gone to sleep]
jonahR has joined #cinch
Spami has joined #cinch
Spami has joined #cinch
Spami has quit [Quit: This computer has gone to sleep]
Spami has joined #cinch
Spami has quit [Quit: This computer has gone to sleep]
postmodern has joined #cinch
Spami has joined #cinch
<
Donovan>
is there any other good documentation on using cinch besides that on rubydoc.info?
<
Donovan>
in particular, how would one connect to multiple IRC networks?
<
Donovan>
I'd like to start each in it's own thread
<
dominikh>
not really, no. especially not if you're looking for "guide" style of documentation.
jonahR has quit [Quit: jonahR]
<
dominikh>
as for multiple IRC networks: multiple instances of bots
<
Donovan>
hmmm, okay.
<
dominikh>
bot1 = Cinch::Bot.new... bot2 = Cinch::Bot.new... Thread.new { bot1.start }; bot2.start
<
Donovan>
yeah, I tried that... I'll keep working on it. Thanks.
<
dominikh>
your loop in line conchbot.rb:87 will block on the first call to bot.start
v0n has quit [Ping timeout: 260 seconds]
jonahR has joined #cinch
<
Donovan>
yes, that's where the Thread.new {} code will go
<
Donovan>
this is far from ready. =)
<
Donovan>
or I may have to rework that entire section, not sure yet
<
Donovan>
right now I just have the conf file and plugins loading correctly
<
Donovan>
if I have to, I'll fork each one out
<
Donovan>
realized I had left some potentially sensitive information in there (nothing earth shattering) so redid the public repo. Whoops.
<
dominikh>
heh, good idea
<
Donovan>
still using weechat, I see. What ever happened to the weechat-ruby?
<
dominikh>
lost interest in maintaining it when a) I was done writing the scripts I needed b) the weechat dev expressed his dislike for the idea
<
dominikh>
since b pretty much meant nobody would really use it, anyway.
<
Donovan>
yeah, I know FlashCode didn't care much for it
<
dominikh>
parts of it were huge hacks, anyway :)
<
Donovan>
too bad, really, but I get A
<
dominikh>
pretty sure it's incompatible with any recent version of weechat, though.
<
dominikh>
nowadays I use a python port of one of the scripts I wrote for weechat-ruby instead :)
<
dominikh>
means I don't even have to maintain the script ;)
<
Donovan>
I've hacked a few weechat ruby scripts myself, now embarking on this bot exercise
<
Donovan>
yea, that's what I did too... first script morphed into a template for the rest
<
Donovan>
(but rest, I meant the two others)
<
Donovan>
oh well, I was simply curious. Thanks.
<
dominikh>
someone once wanted to pick up weechat-ruby and maintain it. never heard back from him.
<
Donovan>
I asked FlashCode about doing it (to help learn the weechat syntax) but was told "don't bother"
ColdBlooder has quit [Remote host closed the connection]
<
dominikh>
he has this broken concept that the scripting API should be identical for all languages
<
Donovan>
yeah, exactly, kinda silly
space has joined #cinch
Spami has quit [Quit: This computer has gone to sleep]