dominikh changed the topic of #cinch to: The IRC Framework | Latest version: Cinch 2.3.1
mayamai has quit [Ping timeout: 250 seconds]
iamayam has joined #cinch
woodruffw has quit [Quit: And then he took off.]
woodruffw has joined #cinch
postmodern has quit [Quit: Leaving]
Lirion has quit [Quit: echo 16i[q]sa[ln0=aln100%Pln100/snlbx]sbA0D4D465452snlb xq |dc]
g7 has joined #cinch
<g7>
How can you listen for a RAW numeric using Cinch, rather than the pre defined things like :message?
<g7>
For example RAW 265
<g7>
?
<g7>
tried on :raw, /265/ do |m|, on :raw, 265 do |m|, on :raw, "265" do |m|
<al2o3-cr>
g7: Have you tried on :"265" do |m| ... ?
<g7>
al2o3-cr: yeah, just causes errors
al2o3-cr is now known as gr33n7007h
gr33n7007h is now known as al2o3-cr
<al2o3-cr>
g7: You sure, I just tried with 903 and it works for me
<al2o3-cr>
as in #=> on :"903" do |m| puts "yada yada" end
irsol has quit [Ping timeout: 276 seconds]
irsol has joined #cinch
<g7>
ah ok, missed the ". is that going to match just when the server sends numeric 903?
<g7>
or when anything happens that contains 903? like a users message for eg
<al2o3-cr>
g7: server sends numeric 903
<g7>
al2o3-cr: ok thanks. do you know how I can hide cinch output when I run a bot?
<al2o3-cr>
g7: not sure you can, but i'm not to certain. best hang around a bit for a positive answer
<al2o3-cr>
log will hide debug output but still contain the raw IRC log and from there on, the levels are rather self-explanatory. (straight from the docs)