dominikh changed the topic of #cinch to: The IRC Framework | Latest version: Cinch 2.1.0
xeviox is now known as xeviox|afk
xeviox|afk has quit [Ping timeout: 244 seconds]
xeviox|afk has joined #cinch
xeviox|afk is now known as xeviox
irsol has joined #cinch
marahin has joined #cinch
<marahin> Heya guys. Is there any method for someone entering the channel? (e.g. so I could make a function with "on :entering (...)")
<dominikh> :join
<dominikh> also triggers for the bot itself.
<marahin> dominikh: thanks a lot, first time checking cinch here, couldn't manage to find it on docs anywhere.. :/
<dominikh> http://rubydoc.info/gems/cinch/file/docs/events.md – that falls into the first category (IRC commands) though
<dominikh> we've been considering including a list of all IRC commands that make for valid events, but that'd be a rather long list, so still debating it
rikai has quit [Ping timeout: 240 seconds]
<marahin> dominikh: http://d.gimb.us/b/72298796f36beaf0ad3f46d0167cbdee.txt - any ideas what's wrong?
<dominikh> look at the example plugins in /examples/plugins/ – plugins do not use "on"
<dominikh> they use match and listen_to
<marahin> oh, I see... :v
<marahin> well that's a pity.
rikai has joined #cinch
rikai has joined #cinch
<dominikh> ergo `listen_to :join, method: :foo; def foo(m); m.reply("Witaj, #{m.user}"); end
<marahin> oh, not that bad then
<marahin> thanks for your patience :'P
<dominikh> you didn't require much of it yet :P
rikai has quit [Read error: Connection reset by peer]
rikai has joined #cinch
rikai has joined #cinch
<marahin> that doesn't work for me, and doesn't even drop an error in the console.
<dominikh> probably doesn't work because google changes their layout every other week
<marahin> I see.
<dominikh> should replace that with something else that's more stable :)
<marahin> dominikh: something particular?
<marahin> duckduckgo maybe? :V
<dominikh> dunno, maybe. but duckduckgo has a proper API
<dominikh> to be fair, the entire idea of example plugins is absurd, there should be a written guide on writing plugins instead
<dominikh> or a list of existing released plugins
cloud|nix has joined #cinch
catepill1r is now known as catepillar
gtech has joined #cinch
gtech_ has quit [Remote host closed the connection]
ILoveYou has quit [Remote host closed the connection]
nOgAnOo has quit [Excess Flood]
<Zackio> dominikh: Are you here? :P
postmodern has joined #cinch
kludge` has quit [Ping timeout: 252 seconds]
kludge` has joined #cinch
postmodern has quit [Quit: Leaving]
ayonix has quit [Remote host closed the connection]
ayonix has joined #cinch
ayonix has quit [Read error: Connection reset by peer]
ayonix has joined #cinch
ayonix has quit [Remote host closed the connection]
ayonix has joined #cinch
xeviox is now known as xeviox|afk
<dominikh> Zackio: want to file a bug so I don't forget?
marahin has left #cinch ["Leaving..."]
onewheelskyward has joined #cinch
skybotalpha has joined #cinch
skybotalpha has quit [*.net *.split]
onewheelskyward has quit [*.net *.split]
onewheelskyward has joined #cinch
skybotalpha has joined #cinch
cadence has joined #cinch
hephaestus_rg has joined #cinch
hephaestus_rg has quit [Quit: hephaestus_rg]
hephaestus_rg has joined #cinch
xeviox|afk is now known as xeviox
<CM-Punk> How do I get my bot to read quit messages. Also is there a way to rate limit things like greetings?
<catepillar> there is a global bot rate limit
<catepillar> anything more than that, you need to supply
<catepillar> as far as not reading quit messages anymore, you can either unregister the handler responsible, or add a condition to exit the handler
<leftylink> my general conception of how to read quit messages which I'm just throwing off the top of my head without looking at docs: listen to a :quit event, the handler method gets passed a Message object, you want Message#text of that
<leftylink> or maybe it was Message#message
<leftylink> something along those lines anyway
<dominikh> Message#message – we like stutter in our APIs
<CM-Punk> Okay
<CM-Punk> Cool
<CM-Punk> So there's no further way, or maybe a gem to do a limit on how many greets it sends...like in the event of a netsplit rejoin?
<catepillar> that would be best implemented by you
hephaestus_rg has quit [Quit: hephaestus_rg]