00:08 <pontiki> hey, folks. this has probably been asked, but i'm having a hard time googling up an answer:

00:09 <pontiki> if i want to use the standard .send method to send a method message to an object, how would I do that if .send is overridden (forex, in a User object)

00:14 <pontiki> ah, .__send__

18:27 <nullProtectorate> hello can someone help me?

19:44 <TieSoul> what do you need help with

21:39 <IotaSpencer> is there a way to put case insensitivity only on the command in match, say match /request .../ but the rest sensitive

21:40 <IotaSpencer> because otherwise everything seems to be lowercase :<

21:59 <leftylink> oh interesting. so make part of a regular expression case sensitive. I don't know if there is easy syntax for that, but match /[Rr][Ee][Qq][Uu][Ee][Ss][Tt] blahblah/ would do it

21:59 <leftylink> IotaSpencer: oh interesting. so make part of a regular expression case sensitive. I don't know if there is easy syntax for that, but match /[Rr][Ee][Qq][Uu][Ee][Ss][Tt] blahblah/ would do it

21:59 <IotaSpencer> I see

21:59 <leftylink> IotaSpencer: or I guess my other option would be to make the entire thing case insensitive, and jsut check for the cas-sensitive part in your handler

22:00 <leftylink> IotaSpencer: or try /(?i:insensitive) sensitive/

22:01 <leftylink> I am just finding out about this myself actually

22:02 <leftylink> yeah cool, looks like it works

22:02 <leftylink> irb(main):001:0> "INSENSITIVE sensitive" =~ /(?i:insensitive) sensitive/

22:02 <leftylink> => 0

22:02 <leftylink> irb(main):002:0> "INSENSITIVE Sensitive" =~ /(?i:insensitive) sensitive/

22:02 <leftylink> => nil

22:03 <IotaSpencer> except it seems that anything in () is taken as an argument in cinch

22:03 <IotaSpencer> well cinch::match

22:04 <leftylink> well of course, that's capture gropus. but () is a capture group, (?i:) isn't a capture group

22:04 <IotaSpencer> hmm

22:04 <IotaSpencer> I'll try it and see if it works

22:05 <leftylink> irb(main):009:0> Regexp.new(/(?i:insensitive) sensitive/).match("INSENSITIVE sensitive")[1]

22:05 <leftylink> => nil

22:05 <leftylink> irb(main):010:0> Regexp.new(/((?i:insensitive)) sensitive/).match("INSENSITIVE sensitive")[1]

22:05 <leftylink> => "INSENSITIVE"

22:05 <leftylink> to demonstrate that (?i:) by it self does not create a capture group

22:06 <IotaSpencer> so (?i:request) ...

22:06 <IotaSpencer> correct?

22:06 <leftylink> also, my Regexp.new is completely unnecessary as the /regexp/ literal form already makes a Regexp

22:06 <leftylink> test it out on rubular.com or an irb

22:06 <leftylink> rubular.com is super useful for these regular expression things

22:10 <leftylink> damn named capture groups are rad, I wonder how these get propagated to cinch... do they turn into named arguments?

22:10 <leftylink> must check

22:20 <IotaSpencer> you mean ?<blah>(.*)

22:20 <IotaSpencer> @ leftylink

22:22 <leftylink> it is what I mean, but from what I can tell they just become positional args. might be a tough problem to solve

22:22 <IotaSpencer> pretty sure a thing I was looking at said that they turn into local vars

22:23 <IotaSpencer> ?<username>([A-Za-z0-9-_) => user = ...

22:23 <IotaSpencer> er

22:23 <IotaSpencer> username = ...

22:26 <IotaSpencer> think it only works that way in statements, not match

22:26 <IotaSpencer> if // =~ ...

22:28 <leftylink> irb(main):009:0> /(?<a>b)/.match('b')['a']

22:28 <leftylink> => "b"

22:28 <leftylink> irb(main):010:0> /(?<a>b)/.match('b').captures

22:28 <leftylink> => ["b"]

22:28 <leftylink> so from the point of view of cinch, a named capture group doesn't really look any different from any other capture group

22:29 <IotaSpencer> ofc not its just referenced in sometimes a easier way

22:29 <leftylink> so may be difficult to actually provide them as named args... ah but if I check MatchData#names before passing

22:29 <leftylink> we could totally make this work

22:30 <leftylink> irb(main):016:0> /(?<a>b) (c)/.match('b c').captures

22:30 <leftylink> => ["b"]

22:30 <leftylink> lolwut

22:31 <leftylink> in the presence of named capture groups, all positional captures... disappear completely? maybe?

22:31 <leftylink> oh this be funky

22:32 <leftylink> ok, so I think I know what I want to happen

22:35 <leftylink> heh dominikh want me to do some work on making this named capture stuff work? so my vision is... if I have match /(?<a>b)/, method: :blah; def blah(m, a: nil); m.reply(a) end; then !b should cause bot to reply with 'b'

22:42 <leftylink> ooh, would need to get around the https://github.com/cinchrb/cinch/blob/master/lib/cinch/handler.rb#L90 - under what circumstances are there going to be extra arguments passed in 'arguments' though, hmmmmm