dominikh changed the topic of #cinch to: The IRC Framework | Latest version: Cinch 2.2.6
_djbkd has quit [Remote host closed the connection]
_djbkd has joined #cinch
_djbkd has quit [Remote host closed the connection]
_djbkd has joined #cinch
sarkyniin has quit [Remote host closed the connection]
_djbkd has quit [Remote host closed the connection]
Azure|dc has joined #cinch
Azure has quit [Read error: Connection reset by peer]
_djbkd has joined #cinch
_djbkd has quit [Quit: My people need me...]
thomas has quit [Remote host closed the connection]
thomas has joined #cinch
bosma has quit [Quit: Leaving]
postmodern has quit [Remote host closed the connection]
postmodern has joined #cinch
postmodern has joined #cinch
postmodern has quit [Changing host]
_djbkd has joined #cinch
_djbkd has quit [Remote host closed the connection]
postmodern has quit [Quit: Leaving]
thomas has quit [Quit: leaving]
Elysia has joined #cinch
Dwarf has quit [Ping timeout: 246 seconds]
Dwarf has joined #cinch
eebs has joined #cinch
sarkyniin has joined #cinch
sarkyniin has quit [Remote host closed the connection]
sarkyniin has joined #cinch
Dwarf has quit [*.net *.split]
Lirion has quit [*.net *.split]
Dwarf has joined #cinch
sarkyniin has quit [Ping timeout: 244 seconds]
Lirion has joined #cinch
sarkyniin has joined #cinch
djbkd has joined #cinch
postmodern has joined #cinch
sarkyniin has quit [Remote host closed the connection]
sarkyniin has joined #cinch
eebs has quit [Quit: Leaving.]
Azure|dc has quit [Quit: Oops.]
Azure has joined #cinch
<BlindSight>
Hmm not sure if it's a bug or me being weird, but if you unregister then re-register a plugin, the timer stops then gets re-registered; however it never restarts
<dominikh>
could be, yeah
aneisf has joined #cinch
<aneisf>
what's the best way to listen for my host being changed (vhost taking effect)? i need to wait for that before joining my channels (+I, based on hostmask with vhost)
<dominikh>
figure out which message the IRC network sends, listen for it
<leftylink>
ahhh I ran into that problem that BlindSight mentioned... we talked about it
<leftylink>
hmm. I don't appear to have the log for that anymore.
<leftylink>
BlindSight: but what I ended up was to add: registered_plugin.timers.each { |timer| timer.start }
<leftylink>
to the load_plugin method
<leftylink>
ah... guess the log containing that is on a computer I can't access right now
<leftylink>
but it's in da code so I found it anyway
<leftylink>
I know that when we talked about it at the time dominikh warned me there was a case where that wouldn't work, but that case doesn't apply to me (I think it's if you have timers that are created but you don't want them to start) so I went ahead with it