From: Shadowfirebird <shadowfirebird@gmail.com>
To: sup-talk <sup-talk@rubyforge.org>
Subject: [sup-talk] Hints on debugging hooks
Date: Tue, 19 Oct 2010 10:18:03 +0100 [thread overview]
Message-ID: <1287479408-sup-4846@blake> (raw)
Hi, I'm new to Sup. (I can code Ruby, a bit, but I'm finding the source hard to read, so configuration is going slower than I would like. It's me, not you...)
Can someone give me some hints on debugging hooks? For example, is there an easy way to get just one message object in the console, so I can play with it?
Is it true that the before-add-message hook can die silently if my code is bad? Will wrapping my code in begin ... rescue ... end guarantee that this doesn't happen?
Ta.
--
"All snakes who wish to remain in Ireland will please raise their right hands."
-- Saint Patrick
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next reply other threads:[~2010-10-19 9:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-19 9:18 Shadowfirebird [this message]
2010-10-19 17:31 ` Michael Stapelberg
2010-10-19 18:18 ` Hamish D
2010-10-20 21:00 ` Shadowfirebird
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1287479408-sup-4846@blake \
--to=shadowfirebird@gmail.com \
--cc=sup-talk@rubyforge.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox