20:09 <txdv> plugin reloading is now supported?

20:28 <leftylink> txdv: eh I wouldn't call it officially supported until it makes it into the main repo (and it hasn't, right? unless I miss something), but it is known how to do

20:28 <txdv> so i have to highlight dominik every day until he pulls it?

20:29 <dominikh> you try that twice and I'll just ban you :)

20:29 <dominikh> it will never make it into the main repo, because it's not Cinch's concern. the reload logic is concerned with the layout of files on your disk; that's not Cinch's concern.

20:29 <txdv> hey, i didnt highlight you, so i still got one to go

20:29 <dominikh> there's code for reloading plugins, it works, it's not part of Cinch :)

20:29 <txdv> yeah, i saw it in cogbot

20:30 <txdv> and he thanked you in the comments

20:30 <txdv> so probably the best way to go

20:30 <dominikh> there's some gist flying around with my original code

20:32 <txdv> ill serach for them

22:29 <proxnal> is there a way to start/stop a channel listener for example in a plugin?

23:20 <leftylink> proxnal: I wish there were so that I don't have to fire a thread when the listener is disabled, but in the absence of that my two solutions are 1) instance var that the listener checks before acting, or 2) unload the plugin!

23:23 <leftylink> there probably is a less nuclear option than "unlaod the plugin" of course, with more internals knowledge on how listeners are registered, so that I just register/unregister the listener on demand...

23:39 <proxnal> yes i've read the source but there is no mention of unregistering when you have registered

23:42 <proxnal> i am now doing it the instance variable way which feels a bit silly

23:44 <proxnal> the idea is to start and stop recording events with a trigger