17:19 <Wobbley> Hmm, what is the syntax to fire off a method on a matching regex message?

17:20 <Wobbley> I saw in the documentation that you can use do/end, but is there a way just to call a method instead?

17:20 <Wobbley> Because this is definately wrong: on :message, 'www.twitch\.tv/([^\s]+)', :method => :get_url_details :(

17:54 <leftylink> Wobbley: that'd be `match` instead of `on` (also pass a regex instead of a string like you currently have)

18:07 <Wobbley> leftylink: How would the syntax look? on :match, /www.twitch\.tv/([^\s]+)/, :method => :get_url_details

18:08 <leftylink> Wobbley: no `on` at all. the method is named `match`. examples dir should have something for you?

18:09 <Wobbley> leftylink: I saw someone else use "listen_to :channel" and "def listen(m)", that seems to work as well. My problem now is that for some reason the regex returns the entire string T_T

18:11 <Wobbley> leftylink: cause I just have to learn2Ruby more :p

18:11 <leftylink> Wobbley: hmm interesting. but I thought listen_to :channel would just fire on all channel messages. I don't know if it took a regex argument (if it does then ok we can carry on... but I notice the listen method was only taking one arg too, so...???

18:15 <Wobbley> leftylink: ouch you are absolutley right, it fires on everything

18:15 <Wobbley> but if it finds no match i can just return

18:15 <Wobbley> anyways brb in 10

18:30 <Wobbley> Well I found my problem leftylink : I needed to use scan, not match. Thanks for the help :)

18:30 <Wobbley> How would you only make the method trigger on a specific message though?

18:42 <leftylink> Wobbley: ah makes sense. I remember scan vs match at some point in the past. I really think https://github.com/cinchrb/cinch/blob/master/examples/plugins/multiple_matches.rb is what you are looking for in only triggering on a specific message

18:44 <Wobbley> leftylink: Thats the thing though

18:44 <Wobbley> I don't want it to match commands?

18:46 <leftylink> I think I don't know what a command is

18:57 <Wobbley> Like !cake

18:59 <leftylink> hmm, but you wouldn't have to put "cake" in your match regex (or string). you could put whatever you want

19:21 <Wobbley> I am not sure if we are talking past each other here, or I am just misunderstanding perhaps

19:26 <leftylink> well I won't begrudge being corrected because I've had to correct some misunderstandings before

19:27 <leftylink> coworker asks me to review code, I leave comments, coworker responds in a way that didn't address what I meant, we go back and forth for about two comments before I just go "I think we are misunderstanding here" and we got ourselves on the same page again

19:27 <leftylink> no fear!

19:28 <leftylink> also needed to have no fear because coworker could be considered to be in a superior position compared to me. can't do it if I am afraid of retribution

19:32 <leftylink> although I guess in that case I had the advantage of being able to walk up to coworker and go "YO we are messed up" and I suppose we lack that option here

19:33 <leftylink> but we do the best we can, I hope